MichaelTamoush
4 years agoQrew Captain
Restructuring my Apps - any easyish way to accomplish this?
We are expanding in a way that makes me need to restructure my app, so that as it grows it makes sense. The best example of what I need to do is with an employees table. I have an employees Table in App A. It has many relationships, both in App A and some cross app relationships (to App AB and AC).
I am going to be creating a number of other Apps for other sister companies. They will share a few things, such as employees. Everything else will be separate.
I would like to make a Global App, with the Employees table in it (and a few other global items). Then I would like to use table syncs to get the employees to each 'cluster' of apps (each sister company will be using a cluster of apps for themselves). I have chosen to sync, so that I don't end up with 15+ apps all related to each other in some way. However, I am open to suggestions on this.
This leads me to my question. Ideally, I would move the Employee table to a global app, then in the original table A, convert the employee table to a sync table. This isnt possible, so I would have to create a new employee synced table, then recreate all relationships (and pipelines/automations) until it works, and then delete the old employee table. I am not a fan of this solution, I think it is too intertwined for me to succeed.
Any thoughts on changing an existing table to instead be synced to another? Or perhaps I am coming at this from the entire wrong direction.
------------------------------
Michael Tamoush
------------------------------
I am going to be creating a number of other Apps for other sister companies. They will share a few things, such as employees. Everything else will be separate.
I would like to make a Global App, with the Employees table in it (and a few other global items). Then I would like to use table syncs to get the employees to each 'cluster' of apps (each sister company will be using a cluster of apps for themselves). I have chosen to sync, so that I don't end up with 15+ apps all related to each other in some way. However, I am open to suggestions on this.
This leads me to my question. Ideally, I would move the Employee table to a global app, then in the original table A, convert the employee table to a sync table. This isnt possible, so I would have to create a new employee synced table, then recreate all relationships (and pipelines/automations) until it works, and then delete the old employee table. I am not a fan of this solution, I think it is too intertwined for me to succeed.
Any thoughts on changing an existing table to instead be synced to another? Or perhaps I am coming at this from the entire wrong direction.
------------------------------
Michael Tamoush
------------------------------