A LOT of issues migrating to V2. Do we need to migrate?
I’ve migrated 2 of my workflows thus far and it’s been a complete pain in the a** so far. My variables keep getting wiped for no reason at all and I have to sit there and replace all of the invalid context variables over and over again and I have no idea why. I’ve probably done this a dozen times now if not more and this is such a waste of time and extremely frustrating.
Do we have to migrate our workflows to V2 or can they continue to run on V1 without any issues? Also do yall have any resources whatsoever to help with migrating workflows efficiently or no? My previous workflows referenced incoming data by using dot notation (e.g. body.firstName, body.Email) but now I’m trying to figure out if I need to define each input or can I simply define the body object as an input and keep the dot notation in place? @Harini @Gaurav Chadha
1 Reply
HI @safir.ali When was the last time you added the variables and noticed this issue?
As we have released a fix for this few hours ago today? Could you please now add the variables/values in the fields of the missing values workflow and ship again?
Regarding the migration workflow, yes your V1 workflows will continue to run as earlier without any issues.
Using the dot notation should remain same, you can reference the trigger data by defining an input and then access it in the Trigger setup as, please refer to second image attached. And the the best part is it will automatically map your inputs to trigger data eliminating the requirement of manually adding dot notation for each inputs.
Here's a sample workflow I've created for you to test this case - https://app.buildship.com/remix/db8f3831-17c8-4b45-a9f8-dad58a685fc6.
Hope this helps.
