I have record A and a record B on same source table but using different sync filters, all the DB writes and updates are happening through record A, so it is holding all the updated values, but record B is not getting synced to update the latest values.I tried establishing one to one relationship between record A and B, using same primary key, but still sync doesn't happen.
Is there any other way to sync the record B whenever an update happens to the source table through record A?
Discussion posts and replies are publicly visible
Shubham Aware Harsha Sharma Stefan Helzle Hima Appian recommends to use sync filters for limiting the rows in records based on required business logics, in this case records won't be in sync unless we specifically use a sync record smart service.If a main case table is being being planned for this scenario, then obviously it would be dependent in multiple process models or write records functions, so updating each one is going to be huge effort.
Honestly, Patching every a!writeRecords() call with a!syncRecords() across multiple process models is a maintenance nightmare.You should try this :- Centralize all writes to one process -> call a!syncRecords() for both Record A and B after each write.OrConsolidate into one Record Type on the shared table -> control data visibility using sync filters, record-level security, or user filters at the interface level -> eliminates sync complexity entirely.