Hi, I copied an app to make a new app, and one of the tables has evolved quite a bit – mostly from adding new rows. Since I don’t want to maintain the table in both apps, I added the evolved table to the older app, thinking I would modify the screens to use the shared table, and eventually remove the older table with fewer rows.
When I added the newer, maintained table, however, the Row ID did not come over. Nor did any of the computed columns. These are both Glide tables. Since each app may need different computed columns, that’s OK, but how can I maintain a relation w/o the Row ID?
I see that user-specific columns seem to work between the two apps (the settings are maintained). I have not tested “row owners” yet. This particular table simulates row owners using filters.
What is considered best practice when sharing a complex table between apps (where the Row ID matters)? This is not simply a lookup table.
New table “linked” to older app:
UPDATE: Making @Owner a “row owner” seems to work. But I had to do it independently in both apps. The setting seems to be independent of the app. Also, renaming the table in one app (the first app to own the table) shows in the list of available tables as renamed, but in the other app, it still has the old name.
Just not sure what I am supposed to be seeing, or how Glide is handling things. I know it would be easy to share a simple lookup table, but this table is more complex, and not sure how changes I make in one app will affect the other app that uses the same table.
And the more I think about it, the more I’m certain that the Row ID is important even in a lookup table, in order to standardize the database. Think about a misspelled word. Easy enough, modify the lookup table and it automatically corrects the spelling everywhere – because it’s tied to a Row ID