Hi Esri Community,
Thanks to the helpful guidance I received earlier, I successfully configured forms in Map Viewer to enable editing of related table records in Experience Builder. It’s great to see this functionality, and I appreciate the effort to bridge the gap between Web AppBuilder and Experience Builder.
However, I’ve noticed a significant limitation:
While it’s possible to control editing permissions (e.g., disabling deletion) for the parent feature layer, there doesn’t seem to be a way to apply similar restrictions to related tables. Even if I disable deletion for the feature layer in the Map Viewer or on the service itself, users are still able to delete records from the related tables.
This lack of granular control over related table permissions presents a challenge, especially when the data in the related tables is critical and should not be deleted accidentally.
Is there currently a way to restrict delete permissions (or any other edit permissions) for related table records in Experience Builder?
If not, are there any plans for enhancements to address this issue in a future release?
In workflows where related tables are used to manage sensitive or interdependent data, the inability to restrict specific editing actions on related records could lead to accidental data loss. Being able to configure related table permissions separately would provide greater control and security.
Any insights, workarounds, or updates on this would be greatly appreciated!
Thank you,
Ali
Do your users have admin level permissions to edit content?
To add further context to @ClayDonaldsonSWCA's question, users with Admin privileges or the owner's of the data can always have access to all editing functions even if some of them have been disabled.
Hello,
I am a colleague of the original poster and actually the one with the issue - I came across this question while searching for a solution this morning!
I can confirm that we do not have Admin Level accounts in this instance.
We are using the Editing Widget in Experience Builder and we have configured the editing through building a form in the underlying Web Map which controls visible fields, read only fields and lets the user access related tables etc. The issue is that while in Experience Builder we can disable delete in any of the Feature Services we seem to be unable to do this for records that are in a related table in the map as a table only (related records that are in as a Feature Service are fine as we can disable the deletion in Edit widget).
Any suggestions would be appreciated!
Cheers
Thank you for posting. This is a bug and the Experience Builder team will look into it.