I am making certain standard object fields required via dynamic forms. The business would like to make the Mailing Address required based on a custom Type field value, but dynamic forms only shows two options - read only and none for address.
Is there any way around this limitation that does not involve creating multiple custom address fields? I have a validation rule for worst case, but hoped I wouldn't need it. Thanks!
@K S From what I can see you do not have the fields with normal behavior being displayed under the opposite condition.
You are adding visibility criteria to that Field component itself, not to the behavior. So you would need to add a second instance of that Field component to show when the conditions of the required component are not met.
Here is a very simplified example:
I have a checkbox field and sample picklist field. I added in an instance with no UI behavior (normal) to display when that field is not required and then a second instance to display when that checkbox is checked to make the field show as required.
