Scenario Builder: make the upgrade of modules easier
Michael White
Now that there are upgrades to the Facebook modules, there should be an easy way to upgrade the modules that we are already using without having to delete and recreate them. I should be able to do this one module at a time so that I can test to make sure things are still working well.
Joscha Götzer: If you wanna go fancy, how about trying to guess the new field names in case of a V2, and showing some validation procedure output that tells the user what he has to fix by hand? :)
-----------------------------------
REPLY: Here is a step-by-step guide How to replace legacy modules with new modules in a scenario:
Your comments/experience/suggestions/etc. are very welcome.
Log In
Christian Lee
This method of replacing modules is almost slower than completely rebuilding the scenarios. This is such an easy to feature to release when modules introduce breaking changes. I cannot believe a better solution doesnt exist.
Julian Lindner
We absolutely need an easier way to upgrade module versions in large, complex scenarios. The current approach is mind-bogglingly manual and time consuming.
Samuel Tingel
Hi, I just wish to support your idea of replacing the versions of the modules. I encounter this now with Monday.com modules and I really hope there can be a more simple, more convenient way to replace all of them by one click - not one by one in hundreds of cases.
Autopilot
Merged in a post:
Being able to update outdated modules without needing to manually recreate the whole flow
Nandan Muthukumar
Kevin Smith
The problem is, the dev tool (F12) only copies mappings frmo old mod to new mod, it SHOULD also update all references to old mod with new mod.
its easy to code...
SrcMod = modules[source)
TarMod = modules[target)
FOREACH module IN module
IF module <> SrcMod THEN
FOREACH mapping IN module.mappings
FOREACH SrcMapping in SrcMod
IF mapping.item = SrcMod.item THEN mapping.item = TarMod.item
NEXT SrcMapping
NEXT mapping
ENDIF
NEXT module
Onur Bolaca
This is still needed for my 100+ flows
David Stanton
+1 for a proper "upgrade", not a "do it again"
akash.paul@integromat.com
Jan Kadela: Hi Jan!
Thank you very much for raising your feature request. We always try our best to keep it same but it would depends on the API service if there is any breaking change we've to upgrade to a newer version of module and in those case things are not in Integromat hands. But We understand you and that's why we've a workaround. Please use Integromat Dev Tool to swap Apps, Modules, connections and Mappings. Please check the Documentation Here
Please check it and let us know your views on it.
Thanks.
Xoel López Barata
Any updates on this? Still a pain in the ass to edit all the references
Michal Máša
Would adding "Replace this module" option in the module's context menu help a bit?
Michael White
Michal Máša: How about "Upgrade this Module"? I don't want to lose any settings from the old one (where possible). "Replace" doesn't give me a warm and fuzzy feeling that my settings will still be there.
Michal Máša
Michael White: You are right, The "Replace this module" would probably just remove the existing module and insert a new one (with a new ID). This way all the module's settings would be gone and references to module's output in the subsequent modules would be rendered invalid. So this is probably not what you wished for ;(
Juilian Kirkness
Michael White: Quite agree - I looked at the document and the technique to upgrade is what I would have expected - but I am not keen on this process - I may have a scenario with say 10 or 20 Knack modules for example - all interrelated - which are providing business logic for client's apps - this process is very dangerous running against a live app!!!!
Load More
→