Scenario Builder: export Blueprint with all the used Data structures
Ashok Mistry
Able to import and export data structures. Ideally any data structure used in a scenario should also export in a Blueprint which it doesn't at the moment.
Log In
Pierre Becher
It's a major limitation that data store structures ar lost and have to be rebuilt from scratch when exporting/importing scenarios, see also here: https://community.make.com/t/data-store-configuration-lost-when-import-blueprint/30948/2
Dailen Gunter
Seems trivial but in terms of backup and retention this is pretty critical. I'm adding some colleagues to our organization and worry if they accidentally delete a data structure how i'll be able to restore it. As some of these automations become "Standard Procedure" for companies, there has to be a way to maintain a "disaster recovery scenario". Like what if somehow an account was hacked and the organization was deleted? Some company operations could come to a grinding halt. Backup, Retention, and Documentation of scenarios and configurations are critical of anything that becomes part of standard procedure for a company's survival.
Dale Georg
This definitely should be a high priority, in my opinion. I have scenarios that I've built using my personal org, and now that they are stable I want to move them into my company's org, which I thought I would be able to do with Export / Import Blueprint. And technically I can, but first I have to manually create all my data structures and data stores. At a minimum, there should be the ability to export data structures, but ideally Export Blueprint would export everything required to actually make the scenario functional.
John K
Really surprised this isn't near the top of the list, its a real issue not being able to properly export/import scenarios (for example between accounts)
Nesim Arslan
yes, i agree
M k
Hi
There should be a way to import/export a scenario, intact.
Mary