I have a template database which mirrors a base database.
The reason for this structure is to keep templates (fake data) separate from real entries, to restrict access, and to ensure a standard.
I want users to be able to click on a button in the template entity to create a duplicate inside the real database.
A couple of hacks I could do, but am not a fan of:
- Create in-place and convert-to — messy
- Temporarily link a new record to the template, populate the fields, then remove the relation
- Try and find a way to script it…?
Is there a solution I’m not seeing?
The good solution would be if we allow to create new entities not linked to current database in Automations. Overall nothing should stop it technically, but we made some bad choices initially in automations. I hope early next year it will be resolved, since we will focus on some improvements in this area soon
1 Like
I’ve personally found it quote helpful to keep this relation from template to the created entity. It’s valuable data.
It allows you to see where the entity came from, and can even have triggers that update the templated entity when the template entity is updated.
Not truly a solution to your question. Why are you you not a fan of having the template entity link to the templated entity?
If you really want to create it without being linked, indeed the best is scripting, or create and unlink.