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:
Issue:
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.
Question:
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?
Why This is Important:
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
