I believe the behavior you are trying to implement is that the column should not be blank during data entry before form save.
If so, as per my understanding, “Required_If” constraint is basically used to check that behavior of the column.
Following are the two excerpts from the help article on the “Required_If” constraint
The Required_Ifcolumn constraint may be used to require a column value of a row be present before the row may be saved. If a required column value is blank, the row cannot be saved.
The Required_If column constraint is a Yes/No expression: if the expression evaluates as TRUE, the column value may not be blank; if FALSE, the column value may be blank.
I believe the “valid_if” constraint checks validity of the column value once the column is non-blank
Thank you. If you could mention more details on your requirement, the community could suggest a combination of Valid_if and Required_if to meet it, if it is feasible.
Your current condition purely checks the blank/not blank value and hence may not work with “valid_if”
I appreciate your point. I believe that is an aspect of implementation in a platform. As per my understanding, it could be a matter of separating behavior between “Required_if” and "Valid_if’
I believe someone from AppSheet team or some other community member could give more insights into this.
You may also wish to consider raising a feature request to implement the behavior.
With Requiered_if I could include the other conditions. But if would reject the user input providing a generic message.
Please note that you could customize even the “This entry is required” message.
However, for these system text messages, customization is more global than local in that it is not row-based but view or user or app-based.