Skip to main content
venkateshg4665
venkateshg4665
June 8, 2026
Question

Sync Smart Service Issue

  • June 8, 2026
  • 4 replies
  • 0 views

Hello everyone,

In the recent update (version 26.1), we received a feature that allows us to create sync-enabled record types using a view as the data source.

However, the Sync smart service is not working with this type of record. Is this an Appian limitation? If yes, how is a sync-enabled record useful in this case? I am aggregating some information in a view and displaying it on the site, and I need up-to-date data. Therefore, I cannot rely on incremental or manual sync. Could you please suggest an appropriate approach?

4 replies

stefanhelzle0001
stefanhelzle0001
June 8, 2026

Well, depending on your use case, a synced record might be the best fit. Or not. In your case disabling sync might be the way to go.

venkateshg4665
venkateshg4665Author
June 8, 2026

Thanks for the reply [mention:a11f77a729fb4db2af76b09948583328:e9ed411860ed4f2ba0265705b8793d05] 
After checking the log files, we found that we were using ROW_NUMBER() to generate a unique key in the view. This was producing a 32-bit BIGINT(21), which we were using as the primary key for the sync record. However, the generated key of type BIGINT (21) was not supported by the record type. After converting the key to text, the issue was resolved.

shubhama926776
shubhama926776
June 8, 2026

Sync Records smart service syncs by record id, but views have no change-tracking, so view-backed synced records only support full sync (not incremental).
Don't use a sync-enabled record for always-fresh data. Use a non-synced record type on the view instead(it queries the view live every time, giving you real-time data).
Sync trades freshness for performance, which is the opposite of what you need.

venkateshg4665
venkateshg4665Author
June 8, 2026

Thanks for the reply [mention:9861aef97eb2483a8b76175d9eda1e37:e9ed411860ed4f2ba0265705b8793d05] 
After checking the log files, we found that we were using ROW_NUMBER() to generate a unique key in the view. This was producing a 32-bit BIGINT(21), which we were using as the primary key for the sync record. However, the generated key of type BIGINT (21) was not supported by the record type. After converting the key to text, the issue was resolved.

Terms & ConditionsAccessibility statement