Thank you!
I have been extremely diligent in the transition to avoid taking any action in an app that will require processing from another. To this point, I haven't made a single cross-app relationship or automation. Our new set of apps are not connected to the old one in any way, I have pulled the data into the new apps using table-to-table field imports that are set to only run manually. With our main focus being performance, I've kept in mind your exact sentiment. If our apps do become reliant, then not only have I still brought back every performance issue, but now I also have our data segregated, creating the worst of both worlds.
You have confirmed by suspicion and I will avoid cross-app relationships altogether.
That being said, my thought regarding sync tables versus automations is that it's simply an assessment of when it would be best to pull data versus push data. Can you think of anything else to keep in mind while building them?
Also, I have noticed an issue in some of our first few tests that I haven't been able to fully diagnose yet. I have a sync table in a department app for Customers. In that app I have a Customers to Tasks relationship. The lookup fields in Tasks seem to clear themselves every time the Customers table syncs. However, when I preview the form I am viewing them on, all of the data on every record appears again. This is very strange and I'm not sure how many different actions allow the field data to re-appear yet, but I'm wondering if this is something you've seen before? (Maybe this warrants it's own post)
