An eagerly loaded screen turns dirty when a SelectionMember is checked for a record.
This looks like a modelling issues. The SelectionMember should only be used in workflows.
SelectionMember could be used in eagerly loaded screens but only with a database field. Using virtual fields in eagerly loaded screens in general does not make any sense as these fields don’t get stored. So the selection would disappear after a reload for example.
So the main use case is really the sequential workflow where the user can select some records and go Next.
If you want to use checkboxes in order to select records for actions, a MultipleSelection action type should be used.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.