Dear all,
I'm facing an issue regarding the full sync of a RecordType via Smart Service, which contains a field with Unique constraint
This is what I'm trying to implement:
The problem is, the sync via Smart Service results in an error due to a violation of a Unique constraint. The source data does NOT violate this constraint. I'm pretty sure the issue is that Appian still holds the old data in the RecordType. So when trying to sync the new data, Appian compares old and new data with the same Unique field, which results in the error.
This error does NOT happen when triggering a full sync manually.
I guess to make my approach (syncing via batches and Smart Service) possible, I have to trigger two automatic syncs:
Does anyone know a better way to implement this? Also, are there any news when it's going to be possible to simply trigger the full sync programmatically withouth having to work with these workarounds?
Thanks and best regards,
Elias
Discussion posts and replies are publicly visible
Regarding the old and new data -- are they different primary key values? For example if you had id = 1 in the database before with UK='a', then deleted and created id = 2 with UK = 'a' in the database, then syncing id = 2 only would not work because it is true that id = 1 is still synced. So if this is the case, then yes, it would be important to loop through multiple rounds of Sync Records to first 'sync' the deleted rows then sync the added rows.
Thanks, I implemented an additional Sync as describred and it's working. Do you have any information considering my second question? Is a feature like that on the roadmap?
This is a popular request definitely. However, in most cases all the data in the source hasn't really changed, so we prefer to focus on identifying solutions that would target and update changed data quickly and efficiently.