Triggered: About Flows and Migration Woes (It's not a bug, it's a feature)

29 maart 2019

I am currently migrating a Document Management business-app from on-prem with Nintex to O365 with Flow. The way i went about it is I first made the Business app in online with some dummy-data. After the  business-app was done, I could migrate all the content to SharePoint online.

So what i did was:

  1. Turned the Flow off, so the on create trigger doesn't go off
  2. migrated the content
  3. Turned the Flow on

No what will happen (GRRRR) is that the flow will still trigger on all those create events. Luckily i just tested a small batch and all mails and notifications were addressed to me. But yeah, this could have gone terribly wrong.

Microsofts opinion about this? It's not a bug, it's a feature!

This is not a bug but an important feature to avoid data loss -- this allows you to temporarily disable a flow, make corrections, and then enable the flow, running it over all of the events that happened in the interim. Without this functionality all of those business critical events would be lost. https://powerusers.microsoft.com/t5/Flow-Ideas/Turning-off-Flow-and-turning-back-on-still-create-new-instances/idi-p/71672

So how would you prevent this from happening? you could do this by:

  1. Export the Flow with the on-create trigger
  2. Delete the Flow with the on-create trigger
  3. Migrate the content
  4. Import the Flow

This is far from ideal, but really something you should do when migrating. You can tell Microsoft to implement a solution for this here: https://powerusers.microsoft.com/t5/Flow-Ideas/Turning-off-Flow-and-turning-back-on-still-create-new-instances/idi-p/71672

Submit a comment