# Getting end users to work with multiple cross-doc tables **URL:** \ **Category:** Ask the Community\ **Created:** [May 23, 2020, 3:47pm UTC](https://connect.superhuman.com/t/getting-end-users-to-work-with-multiple-cross-doc-tables/16168 "2020-05-23T15:47:53Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![Tim\_Sherrod](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/tim_sherrod/32/12708_2.png) [@Tim\_Sherrod](https://connect.superhuman.com/u/Tim_Sherrod)\ **Post date:** [May 23, 2020, 5:23pm UTC](https://connect.superhuman.com/t/getting-end-users-to-work-with-multiple-cross-doc-tables/16168/8 "2020-05-23T17:23:11Z")
Well I think I can use this to modify the row, so I wonder if I just have my main formula set up wrong and it is failing. > [@Pro hack: Trigger cross-doc sync with an action (hidden formula)](https://connect.superhuman.com/t/pro-hack-trigger-cross-doc-sync-with-an-action-hidden-formula/14518/13): > > Let’s say Doc A is a data source and Doc B is where you have the sync table from Doc A. I see the process like this: Doc B inserts a row into Doc A through a Cross-doc action Doc A has an automation listening on new/updated rows in that table you just inserted a row to. When automation triggers, Doc A updates that trigger cell in Doc B through a Cross-doc ModifyRow action. Doc B has an automation listening on that cell change, as per the trick. This triggers the startsync/synctabletable scenar… --- _[View the full topic](https://connect.superhuman.com/t/getting-end-users-to-work-with-multiple-cross-doc-tables/16168)._