Also when I adjust the unique ID column width, it regenerates a new set of numbers for all tables. How do I stop that from happening when I adjust the column width?
You could also use this formula to get the true unique identifier of the row: split(thisRow+"","/").Last()
setting updateContinuosly=false will fix that
Nevertheless, I really would encourage you to consider combining the 3 tables into 1. In general the less tables you have, the better, even if you have some fields that are only relevant to some category of people (for example ‘home owners’) your future self will thank you.
The first (client) table is fetched/synced from a survey using Typeform, I can’t change info or add to that table’s row, so I added a 2nd table for manually added clients. Then a third table for all agents to organize their information, check their leads etc. . .
Is there any way I can optimize my doc?
Also, is the true unique identifier unique across all tables currently exist and will exist on coda?
Source field: ‘Typeform’, ‘Manual’, etc. Default to ‘Manual’.
All the fields you need for the different types (only people data, other business objects should have their separate tables)
Create an automation to add the clients from the Typeform table to your People table.
Create a table for ‘Leads’
Agent field: Relation linking to ‘People’ but making only those with type ‘Agent’ selectable.
Client field: Same but with ‘Client’ types.
Any other fields you might need
No, only within the table. For example if you duplicate a table these UIDs will also be duplicated.
But if you use the simpler formula thisRow+'' it will display the unique id of the table and the unique id of the row separated by a /. The whole string then really is a unique id for any row within a document.