I have a couple of fields that should not be required based on data in the rest of the record. I’d rather not mark them as not required and build a validation rule on the back end. We are using these pages in our community and validation rules are often seen as a gotcha by users who can’t see that it is required until they go to save. Ideas?
We’ve been kicking aroudn the idea of packaging conditional properties with the rendering conditions that we are working on. So for any given component - in addition to building conditions that manage if it should show or hide, conditions could determine whether the field should be required, set its default value, etc. Of course that’s all pie in the sky right now, but its where we are headed.
For now I think the answer is that you could control the client side validation with custom Javascript using a custom renderer. I think thats the best you could do…
1 Like
Hello, Was this ever built into the product?
1 Like
We just put the field twice on the layout - once as required, and conditionally show this field when the field is required. Other time is the not required version. The situation drives whether the user sees the required or not required field.
