Salesforce Fact #823 | Count restriction with repeater and datatable combo in screen flow

With the new Repeater(Beta) component in screen flow, we can repeat the same input structure multiple times as we want but there is no simple way of putting a validation on the count i.e. till how many instances the repeat should happen.

We can use a datatable to show the data entered in the repeater instances and at the same time make use of the minimum selection and maximum selection options to restrict the number of user selections.

In this example, we are using the Repeater component to accept input for the account record fields and in the data table the entered data is shown and the user is allowed to select maximum 3 records, thus imposing the restriction on the count.

Attached are the screenshots.








Comments

Post a Comment

Popular posts from this blog

Salesforce Fact #192 | Call batch apex from flow

Image
Generally apex batch jobs are scheduled to run at particular time intervals. But suppose we have a use case where we need to run the batch job on adhoc basis. We can call the batch apex from a screen flow in that case and the screen flow can be invoked from a button. So, the batch job can be executed on demand. Attached are the screenshots.
Read more

Salesforce Fact #457 | Get current user role name in flow

Image
In apex, in order to get the current user role name we need to query the UserRole object. We cannot get it directly using UserInfo object since it has only one method related to role i.e  getUserRoleId(). Using this Id returned we can get the data from UserRole object. But that is not that complex in flow. In case of flow, we can directly get the current user role name using the syntax: {!$UserRole.Name}. Attached are the screenshots.
Read more