Solved

Multiple records don't sync on same source table

Forum|Forum|4 months ago
March 19, 2026
13 replies
1 view

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?

Best answer by hemnaths589375

This issue has been reported to Appian, and it's fixed as part of latest hotfix version 25.4.597.0.

After environment upgrade, updating the relevant records and remapping the database table helped to overcome the issue.

Thanks all for the inputs.

shubhama926776

Record B won’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.

harshas2775

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.

stefanhelzle0001

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

himab8996

I dont think , we have that option in Appian to trigger record sync automatically, if any changes made in parent table it does not reflect in child table . But you can have scheduled record sync regularly for latest data or use record sync node

mathieud0001

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.

hemnaths589375Author

Thanks [mention:f5e81b8502fa4e77ad12697686a4fc56:e9ed411860ed4f2ba0265705b8793d05] , I tried updating the record to specify the schema like you suggested, but still the sync is not happening as expected.

mathieud0001

1. You can see the schema on both records?

2. You are using the same connected system for both Records?

hemnaths589375Author

[mention:9861aef97eb2483a8b76175d9eda1e37:e9ed411860ed4f2ba0265705b8793d05] [mention:65b14048184a4eb5aff3a76c87b97431:e9ed411860ed4f2ba0265705b8793d05] [mention:a11f77a729fb4db2af76b09948583328:e9ed411860ed4f2ba0265705b8793d05] [mention:1354bb3014d64ba08d28b1dffe953d9c:e9ed411860ed4f2ba0265705b8793d05]

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.

shubhama926776

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.

hemnaths589375AuthorAnswer

This issue has been reported to Appian, and it's fixed as part of latest hotfix version 25.4.597.0.

After environment upgrade, updating the relevant records and remapping the database table helped to overcome the issue.

Thanks all for the inputs.

Sign up

Login with SSO

Login to the community

Login with SSO