We are attempting to conditionalise the Edit/Delete functionality within a table view that is sourced from a data page.
This view is reused in multiple areas and landing pages and we want to ensure Delete can only be accessed by a certain role.
We are able to control this via RBAC, but it presents quite an ugly error rather than removing the Delete option from the table.
This is possible in other table views, but not in this configuration. We are currently on 24.2.
This is not possible @Phill99J. Even the RBAC rules, as you say do not handle this exactly how you would want. There are two items on our backlog in this area, which hopefully will improve authoring and configurations. in the future:
I’ll make sure the team are aware of your feedback here, this helps with prioritisation and impact.
As for immediate solutions, you could create a different view for each of your personas? Or better yet have a view with delete and one without and dynamically show it? Obviously, still keep the RBAC in place to secure it, but then at least it would not show when its not allowed.
That was my gut feel but didn’t want to assume and wondered if it was up and coming. Good to know it’s on the backlog to be addressed.
Separate views was our next approach but wanted to see if there was a way to avoid the duplication.
Thanks!
