Hi, waiting for an implementation of Conditional Fields, there is a special case related to buttons: having a button appear on every entity of a database can be troublesome for data integrity, since the user can invoke its action on entities where it should not be done.
Current button definition does not include setting a condition to activate/show the button, so it seems that currently there is no way of preventing this risk, unless defining multiple views of the same database where the button field appears (for entities in a compatible state) and another view without the field button (for entities in a non compatible state with the button), but it’s not a solution especially when having multiple buttons so we should create as many views as many combinations of buttons states.
What do you think?
Cheers
2 Likes