Sync Smart Service Issue

RE: Sync Smart Service Issue

Goddati Venkatesh — Mon, 08 Jun 2026 12:29:28 GMT

Thanks for the reply Shubham Aware
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.

RE: Sync Smart Service Issue

Goddati Venkatesh — Mon, 08 Jun 2026 12:25:46 GMT

Thanks for the reply Stefan Helzle
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.

RE: Sync Smart Service Issue

Shubham Aware — Mon, 08 Jun 2026 10:41:08 GMT

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.

RE: Sync Smart Service Issue

Stefan Helzle — Mon, 08 Jun 2026 09:05:06 GMT

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.