"I’m looking for an efficient method to duplicate scenarios for different clients, each with their own Airtable database. Currently, I use blueprints, but when I create a new scenario based on a blueprint and connect it to a new Airtable database (identical setup), I lose all field mappings in the Airtable modules.My current workflow:
- Create a blueprint of the original scenario
- Create a new scenario based on the blueprint
- Connect the Airtable modules to the new client’s database
- All field mappings are lost and need to be manually reconfigured
Is there a way to retain the field mappings when switching to a new Airtable database, even if the column names are the same?
I currently don’t use column IDs in the Airtable modules.
Ideally, I’d like to be able to quickly duplicate and adapt scenarios for different clients without having to remap all fields each time by hand. Are there any automated solutions or best practices to streamline this process?Any suggestions are welcome, especially if they can reduce the amount of manual work involved in setting up scenarios for new clients.