We are trying to apply a unique id to an attribute/field when the user adds and saves a point to a feature layer. The unique id is the combination of an attribute value and an integer, Example: STEA123456. 123456 is unknown until the user saves the point because it must be unique.
We added an “AFTER INSERT” trigger to the “Add” table. When a user adds a single point to the feature layer and clicks save, the unique id is generated successfully. The problem occurs when the user adds multiple points and clicks save. I’ve seen two scenarios occur:
1. The address points are added but all have the same unique id.
2. The address points are not added.
Has anyone done a similar activity with versioning? We're wondering if there are any Esri-specific limitations that may cause what we're seeing.
Environment:
Silverlight API for ArcGIS 3.1
ArcGIS Server 10.2
SQL Server 2008 R2 Standard Edition
We added an “AFTER INSERT” trigger to the “Add” table. When a user adds a single point to the feature layer and clicks save, the unique id is generated successfully. The problem occurs when the user adds multiple points and clicks save. I’ve seen two scenarios occur:
1. The address points are added but all have the same unique id.
2. The address points are not added.
Has anyone done a similar activity with versioning? We're wondering if there are any Esri-specific limitations that may cause what we're seeing.
Environment:
Silverlight API for ArcGIS 3.1
ArcGIS Server 10.2
SQL Server 2008 R2 Standard Edition