We have a record type hooked up to a table. Adding new records works well. But, there is an issue with record edits. The record gets updated in DB, but the auto record sync following the record update fails.
Here is data from error email:
Problem: An error occurred in executing an Activity Class. Details: Unable to sync due to a system failure. Recommended Action: Examine the activity class to correct the error and then resume.
Here is some relevant data from tomcat-stdOut.log:
[http-nio-8080-exec-734] ERROR com.appiancorp.record.service.RecordReplicaUpdateService - Loading updates to synced record type(s) in ADS failed, invalidated record type(s): ...com.appiancorp.suiteapi.common.exceptions.AppianException: Unable to sync due to a system failure. (APNX-1-4521-016)...Caused by: com.appian.data.client.AdsUserInputException: APNX-3-1000-030: Invalid transaction data. Cannot update the same entity multiple times in the same transaction. Invalid id(s): ...
Note: Earlier there is a Data Store Entity for the same table. I've tried removing the data store entity, but this error persists.
Discussion posts and replies are publicly visible
Did take a look at this thread? community.appian.com/.../apnx-3-1000-030-record-sync-failure
Is it possible there is an issue with the underlying type in the db?
Hi Mathieu, thanks for the reply and the related thread. The PK in the db is an unsigned int(10) on Auto_Increment. In Appian, it's mapped to a Number (integer) type.
It may be of significance, that the db also has some thing not reflected in Appian:
1. unique composite key made of up three fields
2. Key indexing for six fields
Tried something suggested by another senior DEV that worked:
The Primay Key for the source table was an Unsigned Int. We removed the Unsigned portion, and the recordType is able to sync now without issue.