When using the Sync Records smart service in a process model targeting a service-backed record type, the node appears to only sync the first 100 records (and returns 100 as “Records Updated”) even when I pass more than 100 identifiers.1. Manual sync on the record type successfully syncs all records and respects batching.2. Scheduled sync also syncs all records.3. Smart service only ever syncs the first 100.My integration and sync expression pages correctly and return more than 100 records when called independently, and there is no documented 100-record limit in the Appian documentation.Has anyone else found this to be the case when it is stated to work with up to 1000 records (and does when used with non service-backed records)Thank you.
Discussion posts and replies are publicly visible
There is no explicit documentation confirming or denying the specific “only 100 records updated” behavior for service‑backed record types.
I assume you followed the documentation: https://docs.appian.com/suite/help/25.4/records-data-sync.html#use-the-sync-records-smart-service
AFAIK you can sync 1000 irrespective of record type.Check this documentation properly - https://docs.appian.com/suite/help/25.4/Sync_Records_Smart_Service.html#syncing-data-in-a-service-backed-record-type
Yeah the documentation SAYS 1000, but it is only allowing 100. That's the whole problem I'm seeing. And again its only when using the smart service in the process model, all other syncing works as expected.
You mention 'pages correctly'. Sync Records doesn't support paging, thus the 1000 record limit. Are all 1000 records being returned in a single call?
Of course I followed the documentation and have the sync expression
By paging i mean i have it loop though every 1000 in batches as per the documentation when pulling records to sync. This isn't really relevant to the sync I'm talking about since its in the process model and when testing we never reach the need for batching. For this issue 194 identifiers are passed into the sync records smart service and only ever 100 are returned as "updated".
Ok, it should work with up to 1000, so a couple of things to experiment with before submitting a support ticket:1 - testing with the function call (a!syncRecords) - on a simple interface with a button execution2 - testing with a completely different integration/sync expression/record - just to see if it's related to this particular setup3 - confirmation that only 100 records were actually updated in the database (vs the messaging that '100 are returned as "updated''')