Hi Community,
After importing a previously saved scenario (blueprint), is there a way to maintain all the mapped fields in my Airtable modules after connecting the Airtable module to a new base that is a duplicate of the original Airtable base that was connected to the original scenario?
To be more specific, I created a content publishing tool that I would like to sell to clients. The tool consists of an Airtable base (that I duplicate in the client’s Airtable environment) and of several Make scenarios that power the automations behind the Airtable base.
The issue I am facing is that when I try to setup my Make blueprints in the client’s environment, I loose all the mapping of my Airtable modules even though the database is exactly the same, the names of the fields are exactly the same, and I am not using “column ID” to identify the fields.
Basically, when I connect the Airtable module to a new base, it looses ALL the stored information. Is this something that can be kept if I am using the Make.com team templates system?
Example of a module with everything mapped BEFORE updating to the new Airtable base:
Example of that same module AFTER updating to the new Airtable base (It’s all gone!!):
This issue is massively important for my business, because I intend to sell these setups as Workspaces for clients to use in their environment, and there are so many small mapping details that I cannot just remap the whole scenario every time I do a setup 
Your help would be much appreciated.
Alex