Data Sync For Related Actions Error(While Updating The Data)

If you search that issue identifier in the application server logs, do you find a corresponding error message? That should help you begin to troubleshoot. Also, could you share information about the CDT you're using? Does the process complete successfully?

Thanks for the reply,

The Process completed Successfully

Please Find the attachments for error logs and CDT information Below

There's something weird in that XSD - it looks like all of your "columnDefinition" properties are actually showing as "columnDeTESTition". Can you try to update those and re-upload the XSD? I'd be curious if when you try to write data if the issue is resolved.

You'll likely need to re-sync manually before testing the immediate sync again. If that still doesn't work, can you post the app server log from the time you triggered the immediate sync? The snippet above looks like it's for when you tried to query the synced data, but the issue likely occurred on sync instead of on query.

Thanks for the reply,

The CDT has been corrected and the issue is still raising

Please Find the attachments for error logs and CDT information Below

It's worth checking the setup of your primary key column. Has it been set to UNSIGNED for example? I would suggest testing it with a datatype of INT instead of BIGINT.

I would also review any user filters and the list view for any unmapped columns or links if you have been modifying the record type i.e. look for examples of the annotation being 'exploded' to it's guid. I haven't seen the latter suggestion affect sync but it can cause issues on deployment so who knows.

It's worth checking the setup of your primary key column. Has it been set to UNSIGNED for example? I would suggest testing it with a datatype of INT instead of BIGINT.

I would also review any user filters and the list view for any unmapped columns or links if you have been modifying the record type i.e. look for examples of the annotation being 'exploded' to it's guid. I haven't seen the latter suggestion affect sync but it can cause issues on deployment so who knows.

Given the error message in the logs, I'd suggest opening a support case.

Thanks a lot 

Yes it is working for INT. But it is not working with BIGINT?.But my requirement is to for BIGINT also

For what it's worth (6 months later):

I recently ran into this exact error message (which is still undocumented on the Appian Documentation page: docs.appian.com/suite/help/21.4/Records_Monitoring_Details.html#other-sync-errors) and scenario (writes to DSE consistently caused Record Type's data sync to fail, evem though the data changes _do_ get persisted, and manually running a data sync has no problems). In my case, the underlying database table's PK was configured as INT UNSIGNED. When I updated it to be simply INT, the data sync errors on DSE writes went away.

Any ideas why the use of UNSIGNED on a PK would cause such an issue with Data Sync?

No idea why it is returning error Joseph DeLong