<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Immediate Attribute Update for Generated IDs in Sweet for ArcGIS Without Refresh in ArcGIS Online Developers Questions</title>
    <link>https://community.esri.com/t5/arcgis-online-developers-questions/immediate-attribute-update-for-generated-ids-in/m-p/1674185#M1613</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When adding or splitting a polygon in Sweet for ArcGIS, I want a unique ID to be generated automatically in the background.&lt;BR /&gt;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.&lt;/P&gt;&lt;P&gt;However, the behavior is currently the following:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;The Arcade trigger runs successfully on add or split&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;The unique ID is created, but&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;The ID does not immediately appear in the feature’s attributes&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;The attribute value only becomes visible after a manual refresh&lt;/P&gt;&lt;P&gt;I’ve also verified that &lt;STRONG&gt;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.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Question:&lt;BR /&gt;Is there a way in Sweet for ArcGIS to apply the generated ID immediately to the feature attributes, without requiring a refresh, &lt;STRONG&gt;and without having to loop through all records (which is too slow)?&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Why this matters:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Editors expect the ID to be available instantly after create or split&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Manual refresh breaks the editing flow&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Looking for:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;A way to force an immediate attribute update&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Or confirmation whether this is a technical limitation of the current editing workflow&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;This is my Attribute rule:&lt;/STRONG&gt;&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;return &lt;SPAN class=""&gt;"VLA" &lt;SPAN class=""&gt;+ &lt;SPAN class=""&gt;Text&lt;SPAN&gt;(&lt;SPAN class=""&gt;NextSequenceValue&lt;SPAN&gt;(&lt;SPAN class=""&gt;"seq_bedrijventerreinperceel"&lt;SPAN&gt;), &lt;SPAN class=""&gt;"000000"&lt;SPAN&gt;);&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;P&gt;Any insights into whether this can be handled client-side, via configuration, or via a different trigger approach, &lt;STRONG&gt;without iterating over all existing records, would be greatly appreciated.&lt;/STRONG&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Mon, 09 Mar 2026 15:37:09 GMT</pubDate>
    <dc:creator>Rune_Van_Severen</dc:creator>
    <dc:date>2026-03-09T15:37:09Z</dc:date>
    <item>
      <title>Immediate Attribute Update for Generated IDs in Sweet for ArcGIS Without Refresh</title>
      <link>https://community.esri.com/t5/arcgis-online-developers-questions/immediate-attribute-update-for-generated-ids-in/m-p/1674185#M1613</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When adding or splitting a polygon in Sweet for ArcGIS, I want a unique ID to be generated automatically in the background.&lt;BR /&gt;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.&lt;/P&gt;&lt;P&gt;However, the behavior is currently the following:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;The Arcade trigger runs successfully on add or split&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;The unique ID is created, but&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;The ID does not immediately appear in the feature’s attributes&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;The attribute value only becomes visible after a manual refresh&lt;/P&gt;&lt;P&gt;I’ve also verified that &lt;STRONG&gt;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.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Question:&lt;BR /&gt;Is there a way in Sweet for ArcGIS to apply the generated ID immediately to the feature attributes, without requiring a refresh, &lt;STRONG&gt;and without having to loop through all records (which is too slow)?&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Why this matters:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Editors expect the ID to be available instantly after create or split&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Manual refresh breaks the editing flow&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Looking for:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;A way to force an immediate attribute update&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Or confirmation whether this is a technical limitation of the current editing workflow&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;This is my Attribute rule:&lt;/STRONG&gt;&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;return &lt;SPAN class=""&gt;"VLA" &lt;SPAN class=""&gt;+ &lt;SPAN class=""&gt;Text&lt;SPAN&gt;(&lt;SPAN class=""&gt;NextSequenceValue&lt;SPAN&gt;(&lt;SPAN class=""&gt;"seq_bedrijventerreinperceel"&lt;SPAN&gt;), &lt;SPAN class=""&gt;"000000"&lt;SPAN&gt;);&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;P&gt;Any insights into whether this can be handled client-side, via configuration, or via a different trigger approach, &lt;STRONG&gt;without iterating over all existing records, would be greatly appreciated.&lt;/STRONG&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Mon, 09 Mar 2026 15:37:09 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-developers-questions/immediate-attribute-update-for-generated-ids-in/m-p/1674185#M1613</guid>
      <dc:creator>Rune_Van_Severen</dc:creator>
      <dc:date>2026-03-09T15:37:09Z</dc:date>
    </item>
  </channel>
</rss>

