Assigned
Status Update
Comments
we...@gmail.com <we...@gmail.com> #2
I'd also love to see this as a formula, in order to apply conditional formatting based on the whether the content of a cell passes the data validation rule or not. Something like ISVALID(value).
we...@gmail.com <we...@gmail.com> #3
I'm completely baffled: what's the point of "Data Validation" if there's no way of checking whether the data satisfies the condition? Could we all be missing something?
we...@gmail.com <we...@gmail.com> #4
@marc.art: The validation still validates within the UI itself; it's just that the results of the validation aren't available in code.
go...@chromium.org <go...@chromium.org> #5
This would be extremely helpful! Im looking to optimize my team's workflow and it is counterintuitive and wasteful on resources to reverse engineer the validation just to check if it is valid when that information is already shown in the UI! Please add .isValid()!!
dg...@chromium.org <dg...@chromium.org> #6
This is a blocking feature for implementing a compliance changelog of only valid entries.
we...@gmail.com <we...@gmail.com> #7
Would definitely be useful.
[Deleted User] <[Deleted User]> #8
Can't see why this isn't already available. I hope it is added soon!
te...@gmail.com <te...@gmail.com> #9
I've created a workaround for this issue that works in a very ugly -technically said- and slightly undetermined way.
My problem is that the validation is already done by the SpreadsheetApp, but only visually accessible by the user. It feels like that "you can see but cannot touch" :) It's against the whole idea of GAS.
I'd really love to have this result accessible (the feature implemented).
About the workaround:
It works based on the experience that the web browser implementation of catch() function allows to access thrown errors by the script editor JS code parts.
In case an invalid input into a cell is rejected by a validation rule then the system will display an error message that is catchable by the user written GAS. In order to make it work first the reject value has to be set on the specified cell then its vale has to be re-entered (modified) then -right after this- calling the getDataValidation() built in function allows us to catch the necessary error.
Only single cells can be tested with this method as setCellValues() ignores any data validation restriction (as of today).
Disadvantages:
- The validity won't be necessarily re-checked for this function: checking cell validity right after the value is inserted into it. Therefore the result of this function might be faulty.
- The code messes up the history as cells will be changed - in case they are valid.
I've tested it successfully on both Firefox and Chromium.
function getCellValidity(cell) {
var origValidRule = cell.getDataValidation();
if (origValidRule == null || ! (cell.getNumRows() == cell.getNumColumns() == 1)) {
return null;
}
var cell_value = cell.getValue();
if (cell_value === '') return true; // empty cell is always valid
var is_valid = true;
var cell_formula = cell.getFormula();
// Storing and checking if cell validation is set to allow invalid input with a warning or reject it
var reject_invalid = ! origValidRule.getAllowInvalid();
// If invalid value is allowed (just warning), then changing validation to reject it
// IMPORTANT: this will not throw an error!
if (! reject_invalid) {
var rejectValidRule = origValidRule.copy().setAllowInvalid(false).build();
cell.setDataValidation(rejectValidRule);
}
// Re-entering value or formula into the cell itself
var cell_formula = cell.getFormula();
if (cell_formula !== '') {
cell.setFormula(cell_formula);
} else {
cell.setValue(cell_value);
}
try {
var tempValidRule = cell.getDataValidation();
} catch(e) {
// Exception: The data that you entered in cell XY violates the data validation rules set on this cell.
// where XY is the A1 style address of the cell
is_valid = false;
}
// Restoring original rule
if (rejectValidRule != null) {
cell.setDataValidation(origValidRule.copy().setAllowInvalid(true).build());
}
return is_valid;
}
Finally let me express my gratitude for all the great works of the developers! With their shared tools/system I can solve many logistical problems of my and others' lives... Cheers!
On this issue: Hurry up guys!
My problem is that the validation is already done by the SpreadsheetApp, but only visually accessible by the user. It feels like that "you can see but cannot touch" :) It's against the whole idea of GAS.
I'd really love to have this result accessible (the feature implemented).
About the workaround:
It works based on the experience that the web browser implementation of catch() function allows to access thrown errors by the script editor JS code parts.
In case an invalid input into a cell is rejected by a validation rule then the system will display an error message that is catchable by the user written GAS. In order to make it work first the reject value has to be set on the specified cell then its vale has to be re-entered (modified) then -right after this- calling the getDataValidation() built in function allows us to catch the necessary error.
Only single cells can be tested with this method as setCellValues() ignores any data validation restriction (as of today).
Disadvantages:
- The validity won't be necessarily re-checked for this function: checking cell validity right after the value is inserted into it. Therefore the result of this function might be faulty.
- The code messes up the history as cells will be changed - in case they are valid.
I've tested it successfully on both Firefox and Chromium.
function getCellValidity(cell) {
var origValidRule = cell.getDataValidation();
if (origValidRule == null || ! (cell.getNumRows() == cell.getNumColumns() == 1)) {
return null;
}
var cell_value = cell.getValue();
if (cell_value === '') return true; // empty cell is always valid
var is_valid = true;
var cell_formula = cell.getFormula();
// Storing and checking if cell validation is set to allow invalid input with a warning or reject it
var reject_invalid = ! origValidRule.getAllowInvalid();
// If invalid value is allowed (just warning), then changing validation to reject it
// IMPORTANT: this will not throw an error!
if (! reject_invalid) {
var rejectValidRule = origValidRule.copy().setAllowInvalid(false).build();
cell.setDataValidation(rejectValidRule);
}
// Re-entering value or formula into the cell itself
var cell_formula = cell.getFormula();
if (cell_formula !== '') {
cell.setFormula(cell_formula);
} else {
cell.setValue(cell_value);
}
try {
var tempValidRule = cell.getDataValidation();
} catch(e) {
// Exception: The data that you entered in cell XY violates the data validation rules set on this cell.
// where XY is the A1 style address of the cell
is_valid = false;
}
// Restoring original rule
if (rejectValidRule != null) {
cell.setDataValidation(origValidRule.copy().setAllowInvalid(true).build());
}
return is_valid;
}
Finally let me express my gratitude for all the great works of the developers! With their shared tools/system I can solve many logistical problems of my and others' lives... Cheers!
On this issue: Hurry up guys!
we...@gmail.com <we...@gmail.com> #10
I'm desperate for this method to be added! Please please please do it soonest possible! Thank you!
da...@chromium.org <da...@chromium.org> #11
Yes please implement this. I suppose the data could be checked against the data validation rules before setting the values, but that would really slow the write process down. Not to mention how much of a pain it would be to code all the validity checks to accommodate all the different possible data validation rules.
I've been starting to use Google Sheets to serve some of our company's data storage in place of data typically stored in a SQL database, but the hard data validation rules are an essential part to maintaining data integrity in the way that's possible with a SQL database.
I've been starting to use Google Sheets to serve some of our company's data storage in place of data typically stored in a SQL database, but the hard data validation rules are an essential part to maintaining data integrity in the way that's possible with a SQL database.
da...@chromium.org <da...@chromium.org> #12
Please add this. It will bring down so much bad code that I have put in place due to lack of this function.
da...@chromium.org <da...@chromium.org> #13
Please add this in asimple manner: isValid() true or false
ve...@chromium.org <ve...@chromium.org> #14
I would say the methis should be intiutive to read.
Range.dataValidate() :: [][]bool
Since we are doing DataValidations ...
Range.dataValidate() :: [][]bool
Since we are doing DataValidations ...
te...@gmail.com <te...@gmail.com> #15
I need it like a thirsty desert traveler needs a few drops of water.
te...@gmail.com <te...@gmail.com> #16
I need it like a few drops of water need hydrogen and oxygen
en...@chromium.org <en...@chromium.org> #17
Must I beg?
su...@chromium.org <su...@chromium.org> #18
Seems that begging is necessary...
ra...@microsoft.com <ra...@microsoft.com> #19
Also require this, so i can track any validations fails centrally, without logging into each spreadsheet and sheet to check which is time consuming.
wi...@microsoft.com <wi...@microsoft.com> #20
OK Google... We know you can do it !
su...@chromium.org <su...@chromium.org> #21
Nearly 5 years later and still no change..
I don't think this will happen
I don't think this will happen
ma...@gmail.com <ma...@gmail.com> #22
+1
di...@gmail.com <di...@gmail.com> #23
It would be very cool
we...@gmail.com <we...@gmail.com> #24
+1
ky...@chromium.org <ky...@chromium.org> #25
+1
ky...@chromium.org <ky...@chromium.org> #26
+1
ky...@gmail.com <ky...@gmail.com> #27
+1
di...@gmail.com <di...@gmail.com> #28
+1
di...@gmail.com <di...@gmail.com> #29
+1
ky...@chromium.org <ky...@chromium.org> #30
+1
ra...@microsoft.com <ra...@microsoft.com> #31
+1
pa...@gmail.com <pa...@gmail.com> #32
+1
ra...@microsoft.com <ra...@microsoft.com> #33
+1
hi...@chromium.org <hi...@chromium.org> #34
+1 would be incredibly helpful to just have an ISVALID() formula that returns TRUE has a legit data validation value and FALSE if somebody entered a value into the cell that doesn't match a data validation value. Simple addition to Google Sheets that would make tons of people happy.
pa...@gmail.com <pa...@gmail.com> #35
+1 Hoping...
pe...@chromium.org <pe...@chromium.org> #36
This would be extremely helpful!
Strange that it is not yet implemented, or able to get error validation.
+1
Strange that it is not yet implemented, or able to get error validation.
+1
di...@gmail.com <di...@gmail.com> #37
+1
pe...@chromium.org <pe...@chromium.org> #38
Please add this
pa...@gmail.com <pa...@gmail.com> #39
+1
is...@google.com <is...@google.com> #40
+1
zh...@bytedance.com <zh...@bytedance.com> #41
+1
ra...@microsoft.com <ra...@microsoft.com> #42
+1
jb...@gmail.com <jb...@gmail.com> #43
+1
zh...@bytedance.com <zh...@bytedance.com> #44
+1
ra...@microsoft.com <ra...@microsoft.com> #45
+1
jb...@gmail.com <jb...@gmail.com> #46
+1
ra...@microsoft.com <ra...@microsoft.com> #47
+1
jb...@gmail.com <jb...@gmail.com> #48
+1
jb...@gmail.com <jb...@gmail.com> #49
+1
pa...@gmail.com <pa...@gmail.com> #50
+1
zh...@bytedance.com <zh...@bytedance.com> #51
+1
le...@google.com <le...@google.com> #52
Is somebody working on this one?
pe...@chromium.org <pe...@chromium.org> #53
I'm an experienced app developer and just starting w/ Appscript to customize my client's google sheets. I realized that this simple but critical function-- check if a cell value satisfies a data validation, or if satisfies the conditional formatting condition-- is missing!! Really surprised and disappointed. Tried to find a work-around but apparently I couldn't use some very useful built-in functions such as ISEMAIL within appscript. Lack of these features are quite discouraging to diving into Google Workspace Dev seriously. HOPEFULLY this feature will be RELEASE SOON!
ra...@microsoft.com <ra...@microsoft.com> #54
+1 for sure!
pa...@gmail.com <pa...@gmail.com> #55
@co...@geeksconnect.com
" HOPEFULLY this feature will be RELEASE SOON!"
Been asked since 2016 with no significant progress.
I think there´s more chance of google redoing their whole platform services (which they do frequently) at this point that getting some of these basic stuff.
Would not hold my code waiting for it.
Best worst solution might be to write your validation as a conditional to a temporary (or permanent) cell and read the value of the result I guess...
Haven´t used this in a while just because it´s not practical.
" HOPEFULLY this feature will be RELEASE SOON!"
Been asked since 2016 with no significant progress.
I think there´s more chance of google redoing their whole platform services (which they do frequently) at this point that getting some of these basic stuff.
Would not hold my code waiting for it.
Best worst solution might be to write your validation as a conditional to a temporary (or permanent) cell and read the value of the result I guess...
Haven´t used this in a while just because it´s not practical.
di...@gmail.com <di...@gmail.com> #56
+1
pa...@gmail.com <pa...@gmail.com> #57
+1 & holding my breath.
we...@gmail.com <we...@gmail.com> #58
+1
ya...@gmail.com <ya...@gmail.com> #59
+!
[Deleted User] <[Deleted User]> #60
+1
[Deleted User] <[Deleted User]> #61
+1 as well!!
es...@gmail.com <es...@gmail.com> #62
+1
ma...@gmail.com <ma...@gmail.com> #63
+1
ra...@microsoft.com <ra...@microsoft.com> #64
+1
jb...@gmail.com <jb...@gmail.com> #65
+1
es...@gmail.com <es...@gmail.com> #66
+1
pa...@gmail.com <pa...@gmail.com> #67
+1
ra...@microsoft.com <ra...@microsoft.com> #68
+1
es...@gmail.com <es...@gmail.com> #69
+1
te...@gmail.com <te...@gmail.com> #70
+1
lu...@onet.pl <lu...@onet.pl> #71
+1
le...@gmail.com <le...@gmail.com> #72
+1
un...@gmail.com <un...@gmail.com> #73
Comment has been deleted.
il...@gmail.com <il...@gmail.com> #74
Comment has been deleted.
ni...@gmail.com <ni...@gmail.com> #75
+1
fl...@gmail.com <fl...@gmail.com> #76
+1
sa...@gmail.com <sa...@gmail.com> #77
+1. Add isValid() method
br...@gmail.com <br...@gmail.com> #78
+1
Above suggested a good hack but "try{} catch(e){}" code section takes a long time ( >120 sec). If it processes 3 cells, then we get "Exceeded maximum execution time".
Need a solution from Google.
Above suggested a good hack but "try{} catch(e){}" code section takes a long time ( >120 sec). If it processes 3 cells, then we get "Exceeded maximum execution time".
Need a solution from Google.
do...@gmail.com <do...@gmail.com> #79
+1
di...@gmail.com <di...@gmail.com> #80
+1
It's unfortunate that after the better part of a decade since the original ask, it's pretty clear Google doesn't seem to have the time of day (or care?) to implement this pretty useful feature. Would enjoy having it nonetheless, so I'll continue the bump.
I checked out the Developer References for Apps Script, there is a DataValidation section that I thought would resolve my use-case, but unfortunately after some experimentation it failed to do the trick. I am using a Data Validation that rejects inputs that are not given in the dropdown menu, however I am using a query-based two-layer data validation dropdown system (in other words, my first drop down menu alters a query range that influences what options my second dropdown menu offers). When I change the selection of the first dropdown to something with new options in the second dropdown menu, the selected option remains even though it is invalid in the second dropdown menu. getAllowInvalid() returns "false" in that it will reject any input that fails validation, however when I use getCriteriaValues() to determine a true/false difference between the first menu (which should be valid and TRUE) and the second menu (which is invalid and should be FALSE) they both return TRUE.
Ergo, the currently implemented system is flawed and does not satisfy the simple requirements that my needs nor the needs of many on this 8-year old tracker. I will be looking into an onEdit script to blank out the second dropdown menu as a bandage fix, but it is exactly that: a bandage.
It's unfortunate that after the better part of a decade since the original ask, it's pretty clear Google doesn't seem to have the time of day (or care?) to implement this pretty useful feature. Would enjoy having it nonetheless, so I'll continue the bump.
I checked out the Developer References for Apps Script, there is a DataValidation section that I thought would resolve my use-case, but unfortunately after some experimentation it failed to do the trick. I am using a Data Validation that rejects inputs that are not given in the dropdown menu, however I am using a query-based two-layer data validation dropdown system (in other words, my first drop down menu alters a query range that influences what options my second dropdown menu offers). When I change the selection of the first dropdown to something with new options in the second dropdown menu, the selected option remains even though it is invalid in the second dropdown menu. getAllowInvalid() returns "false" in that it will reject any input that fails validation, however when I use getCriteriaValues() to determine a true/false difference between the first menu (which should be valid and TRUE) and the second menu (which is invalid and should be FALSE) they both return TRUE.
Ergo, the currently implemented system is flawed and does not satisfy the simple requirements that my needs nor the needs of many on this 8-year old tracker. I will be looking into an onEdit script to blank out the second dropdown menu as a bandage fix, but it is exactly that: a bandage.
ti...@gmail.com <ti...@gmail.com> #81
Google doesn't care. Share this on twitter... it wont matter. This project is dead. Do much potential lost. The API provided doesn't work as documented. Its broken and will never work. Stop using Google services.
ti...@gmail.com <ti...@gmail.com> #82
+1
lu...@onet.pl <lu...@onet.pl> #83
+1
why google doesn't care?
why google doesn't care?
ab...@gmail.com <ab...@gmail.com> #84
+1 cmon it has been almost 10 years
ra...@microsoft.com <ra...@microsoft.com> #85
+1
jb...@gmail.com <jb...@gmail.com> #86
+1...million
pe...@gmail.com <pe...@gmail.com> #87
+1
di...@gmail.com <di...@gmail.com> #88
+100
pa...@gmail.com <pa...@gmail.com> #89
+1
ra...@microsoft.com <ra...@microsoft.com> #90
+100
pa...@gmail.com <pa...@gmail.com> #91
+++ would be useful. Want to make sure validation requirements are met before running
we...@gmail.com <we...@gmail.com> #92
+1
pa...@gmail.com <pa...@gmail.com> #93
+1
lu...@onet.pl <lu...@onet.pl> #94
For me, the chessboard disappeared after the update.
pa...@gmail.com <pa...@gmail.com> #95
"After the fix, instead of checkerboard artifacts, sometimes another tab's partial content becomes visible on the current tab in chromium-based browsers... This has never happened before the fix."
This has been happening for me since the checkerboard pattern appeared, it is also more frequent than the checkerboard patterns. I'm on Win10 by the way, so I still don't have the so called fix. I will attach the log Microsoft asked from you, if anything else is needed, let me know.
Edit: Also, I watch a lot of content with subtitles, and the subtitles are also behaving like this, so the previous line comes back for a moment, it's happening everywhere (YouTube, (HBO) Max, etc.)
This has been happening for me since the checkerboard pattern appeared, it is also more frequent than the checkerboard patterns. I'm on Win10 by the way, so I still don't have the so called fix. I will attach the log Microsoft asked from you, if anything else is needed, let me know.
Edit: Also, I watch a lot of content with subtitles, and the subtitles are also behaving like this, so the previous line comes back for a moment, it's happening everywhere (YouTube, (HBO) Max, etc.)
zm...@google.com <zm...@google.com> #96
[gpu triage] This is a long standing bug, drop to P2
ne...@gmail.com <ne...@gmail.com> #97
Comment has been deleted.
ne...@gmail.com <ne...@gmail.com> #98
After fixing the checkerboard, there is a chance of catching the following rendering error ( 26100.1000 and 22631.3737 ) Microsoft, can you seriously not fix this??? Your capitalization is $3.321 Trillion
di...@gmail.com <di...@gmail.com> #99
I do not experience that issue and it looks like one fixed by nvidia already in R540 onwards.
Description
Chrome Version : 115.0.5736.0 (Official Build) (64-bit)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari: PASS
Firefox: PASS
Edge: FAIL (Because it's also based on chromium)
Any animation or edit in the html or css seems to be able to trigger these artifacts randomly every few seconds. Sometimes they are white squares and sometimes black squares.
But one scenario in which a lot of artifacts appear is when I'm on a personal YouTube playlist webpage that displays at least 20 playlist items and YouTube's miniplayer in the bottom right corner of the webpage. Then a lot of artifacts appear when I drag playlist items to other positions.
Requirements:
Reproduction steps:
Prerequisites: Meet the requirements above. (And don't use DevTools or a screenrecorder to record this bug, use a camera instead.)
(1) (Optional, if not already done earlier) Create a personal playlist on youtube.com with at least 20 videos
(2) Go to the playlist's webpage
(3) Click on a video in the playlist
(4) Pause the video
(5) Click on the playlist title to navigate back to the playlist page
(6) The playlist page should now also display a miniplayer at the bottom right of the webpage that contains the video you had just clicked
(7) Scroll down to the bottom of the playlist
(8) (Optional, if not already done at the start) Close any other open Chrome or Chromium windows.
(9) Drag up to 5 times a video for at least 5 seconds to the left, right, up and down. That should be a large enough timespan to trigger these checkerboard artifacts.
Triage steps:
I believe this is a regression, because I can reproduce this in Chromium version 115.0.5736.0 build 1136075 and later. But not in version 115.0.5736.0 build 1136035 and earlier. I also noticed that ANGLE was updated between these builds from version 2.1.20985 to 2.1.20986 when I compared the information in chrome://gpu. So, this could be a regression in ANGLE.
I've compared the following Chromium build snapshots:https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win_x64/1136035/ https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win_x64/1136075/
Build 1136035:
Build 1136075: