*Reposting as thought i had the solution but turns out not*
Hi there,
I recently migrated the feature layer that my survey points to to SQL Server. Since then the object id's have been jumping around all over the place. this was not really an issue until i noticed that when editing a survey, the repeats seem to load in to the survey ordered by their objectid and not by the order they were recorded in. I guess the survey loads in the features in the order they are in the table (which is ordered by objectid).
For example:
1. submit survey with two repeats with names A and B (repeats receive object id's 1012 and 1013)
2. edit survey and add a third repeat named C (receives object id of 412)
3. edit survey again - repeats are now ordered C, A, B
this is quite frustrating as i have other calculations that used indexed-repeat() and therefore need the repeats to stay in the order they were originally recorded in. Also would be nice to have the data in the table in some kind of logical order as people can view and interact with it in experience builder.
Questions:
a) does anyone know why the objectId's are behaving like this, is there a way to stop this behavior, or at least stop them from ever decreasing.
b) is there a way to order the table in the sde by a field other than objectId, by created_date for example?
Cheers
Cheers
