When adding or splitting a polygon in Sweet for ArcGIS, I want a unique ID to be generated automatically in the background.
This is done using an Arcade trigger that reads and updates a sequence table added to the web map. The trigger logic works correctly: a new unique ID is generated and stored.
However, the behavior is currently the following:
The Arcade trigger runs successfully on add or split
The unique ID is created, but
The ID does not immediately appear in the feature’s attributes
The attribute value only becomes visible after a manual refresh
Question:
Is there a way in Sweet for ArcGIS to apply the generated ID immediately to the feature attributes, without requiring a refresh?
Why this matters:
Editors expect the ID to be available instantly after create or split
Manual refresh breaks the editing flow
Looking for:
A way to force an immediate attribute update after the Arcade trigger
Or confirmation whether this is a technical limitation of the current editing workflow
Any insights into whether this can be handled client-side, via configuration, or via a different trigger approach would be greatly appreciated.