Cross-App Relationship v. Sync Table
I'm in the beginning stages of building a platform of applications for my company's facilities' managers. I've built an application named Facilities, which I will use as my master app. I'll have aroun...
Forum Discussion
There are a few downsides to doing cross-app relationships.
One: Any user of the child apps, also has to be a user of the parent app with permissions to see the information of the said "facility". Otherwise the dropdown fields appear blank.
Two: I've heard that this can cause performance issues, especially if you want to pull summary information back to the facility
The big question is: Why do you want them to be separate apps, why not keep it all together? This will give you a lot more flexibility down the road and avoid any synced tables (which is very finicky, and not very easily modified)
One: Any user of the child apps, also has to be a user of the parent app with permissions to see the information of the said "facility". Otherwise the dropdown fields appear blank.
Two: I've heard that this can cause performance issues, especially if you want to pull summary information back to the facility
The big question is: Why do you want them to be separate apps, why not keep it all together? This will give you a lot more flexibility down the road and avoid any synced tables (which is very finicky, and not very easily modified)
- Hi Matt, Thanks for the response. To answer your question, I don't really know why I Would separate them all out. This makes me re-think my strategy - thank you! I think I Will go the cross-app route and combine multiple apps into fewer.
- There is a reason to separate them. If you would want to give each facility manager full access to make app changes without affecting the facility table or other peoples info.
