Immediate Attribute Update for Generated IDs in Sweet for ArcGIS Without Refresh

Rune_Van_Severen

 

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 Attribute rule that uses a sequence table. 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

  I’ve also verified that when ‘Wait for server triggered changes’ is checked in the Data Processing settings of Sweet, nothing changes: the ID still only appears 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, and without having to loop through all records (which is too slow)?

  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

    • Or confirmation whether this is a technical limitation of the current editing workflow

      This is my Attribute rule:

      return "VLA" + Text(NextSequenceValue("seq_bedrijventerreinperceel"), "000000");

       

      Any insights into whether this can be handled client-side, via configuration, or via a different trigger approach, without iterating over all existing records, would be greatly appreciated.

Sweet.png

Esri Community Post 23112022, picture 2.png

AlfredBaldenweck_0-1743106396023.gif

RPGIS

Hi @Rune_Van_Severen,

The issue lies on line 9 where you simply need to replace the line with NextSequenceValue(<name>).

Note: You need to run the "Create Database Sequence" tool in prior to running the updated line of code.

and then in the line update it with the name as shown here. NextSequenceValue(GenerateNumber)