Wait for server triggered changes

The Wait for server triggered changes setting is used when working with data stored in an Enterprise Geodatabase that relies on server‑side logic to populate or modify attributes during create or edit operations (for example, Attribute Rules that generate unique IDs).

When Wait for server triggered changes is enabled, Sweet waits for server‑side processing to complete before displaying feature properties. This ensures that attributes populated by the server, such as calculated or system‑generated values, are immediately visible to the user. Enabling this setting may increase the time required to create or update features, as Sweet must wait for server‑triggered changes to complete before continuing.

When this setting is disabled, server‑generated attribute updates are not immediately reflected. Updated values will only appear after the data is reloaded, such as by refreshing the view or restarting Sweet.