Multiple records don't sync on same source table

Question

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?

Shubham Aware · Answer

Record B won&rsquo;t auto‑sync just because Record A updates the same table. Explicitly trigger a sync on Record B (a!syncRecords) on the primary‑key values after any update, so Record B explicitly pulls the latest data from the source.

Harsha Sharma · Answer

which ever record type is configured in the write records will be synced. Hence record A is synced. If you want record B to be synced every time record A is updated the add a sync record smart service after write records A node so that record B is synced.

Stefan Helzle · Answer

There is no automatic way to do this. Use a sync records node.

Mathieu Drouin · Answer

If you've configured 2 records on the same source table it should sync automatically but you need to use the same connected system. 
 Though you need to be sure that both Records are on the same version. You need to make sure they both have the schema specified. You can upgrade the record type by simply remapping the data source.

Shubham Aware · Answer

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. Or Consolidate 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.