IsNull doesn't work with the required fields
Hi, I have a problem with the "IsNull" function and the date field. My date field "Assignment End Date (DD-MM-YYYY)" is required and of course it is visible on the form. I also have a formula - Ri...
Forum Discussion
OK, right, I see that behaviour now too. It is odd that the ??? result only occurs when you make it blank after filling it in.
So sorry but after all that we are where we were. I tried making a formula to detect the ??? but its not really a ??? result, its note like an @ERR result in excel which then contaminates formulas which refer to that cell.
Plan B could be to make a form rule to always fire (uncheck the checkbox) to copy the value of the date field to a non required date field that you use in the warning formula. The mirror field will need to be on the form, even if in a hidden field.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
So sorry but after all that we are where we were. I tried making a formula to detect the ??? but its not really a ??? result, its note like an @ERR result in excel which then contaminates formulas which refer to that cell.
Plan B could be to make a form rule to always fire (uncheck the checkbox) to copy the value of the date field to a non required date field that you use in the warning formula. The mirror field will need to be on the form, even if in a hidden field.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
Thank you for your answer.
So this is another bug workaround. It allows you to keep the fields required at the level of its properties, but it forces adding "unnecessary" fields to the entire table.
Do you know if and when this bug will be fixed in QB?
------------------------------
Jacek Lewandowski
------------------------------
- Realistically, I doubt that they will consider it a bug and if so, I doubt it would be a high priority. So I suggest that you plan to have a work around or else make the field not required at the field level.
An alternative to Required fields at the field level is to set up Custom Data Rules. Just thought of that now. I believe that will totally solve your issue by allowing you to make the field not be required but block the save in all modes (Grid edit, import, Automations etc ) if not provided.
Here is the help for Custom Data Rules.
https://help.quickbase.com/user-assistance/formulas_custom_data_rules.html
I think the help article is a bit incoherent.
They should lead by
1. Enable Custom data rules on a table by the checkbox in Advanced Properties
2. Make a formula which calculates a text error message to the user.
3. The save will be blocked if the error message calculates to not being blank.
4. If not blank the message will be displayed and he save will be aborted.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
