I have a select that I want to duplicate to multiple database locations (perhaps even using the values to link two entities automatically).
As since this release, it has been possible to copy the select from one database to another.
However, due to the maintenance required to keep these two or more copies of the list synced, it’d likely be better suited stored as its own database.
The issue I see is in converting the existing data; what happens to the old field when a new relationship is added?
If the name is an exact match, then setting up ‘Automatically link A to B’ shouldn’t be too difficult. I’m not too concerned there (though maintaining the link after deleting the original field would break this, no?)
But all of the views that looked at the old select field will require updating—forms and entity views included—and it will also break all reports.
Could you perhaps consider the ability to generate a clean new database from a select, link entities up automatically, and re-route the references so it’s a seamless experience? Huge ask, I know.
It’s recommended that we use the AI Assistant for this: Convert select fields into regular databases - #23 by carson
Although I do believe the request should remain open for voting, as AI credits are limited and this feature is likely needed a lot in the first few months of setting up a workspace
I need this now too… While its not hard to create and replicate, it gets very hard when there are dozens of views, rules, etc which depend on that select field…
The reason it’s needed is that now the select field needs to part of the templating, and I prefer to template using the same database (name changes change everything), and adding an option is added everywhere, etc.
Doing this with selects isn’t ideal. That said, will probably stick to selects for now until this feature is released since refactoring the views and automations has a higher chance of things breaking (for private views and user made views) than the selects.