Hello everyone,
I have some general questions about the flow identifier and 1 specific problem.
First the general question i have a flow in a solution and it has an different identifier if i get it under my flows then when i go the the solution and get the identifier. But it's the same flow with the same steps and run history. Its also shows the same solution in the flow details. But the identifier is different.
And now my problem i use a flow as a button from inside a SharePoint list column. You have to Format the collumn with some code to trigger the flow from the button insde the SharePoint column. If the flow is in the default environment you can use the flow id, but if the flow is in another environment, you have to use the flow identifier. The flow i want to trigger is in a solution, because it has a child flow aswell. The flow works fine but every few days it stopps working, because the flow can't be found and when i get the flow identifier it changed from the last time i checked. If i then switch to the new identifier in the format collumn code it works again.
To specify a few more points:
1. I always used the flow identifier from inside the solution. Not freom the flow you find under "my flows"
2. I didn't reimport the solution or something. I modified the flow but that shouldn't change the flow identifier, if i made some changes to the flow right?
Did anyone else encounter this problem with flows triggered from inside a SharePoint column regarding the flow identifier?
Thanks for your help!
I had the same issue again. Changed the Flow published the changes and checked the identifier still the same. Today i get a message from a user the button isn't working and i checked the identifier and it changed.
It really easy to fix but the user lose trust in the automation if it is not always available and it looks like the change is random.
Does anyone have a solution for this or is having the same problem?
Hi @duds_sn ,
Did you talk to Microsoft about this? I am not sure if this is something for a ticket or if it is working as intended (but this would be really bad for the implementation into a SharePoint list)
Hi @PowerNaps, I'm facing the same issue: Republishing the flow is changing the flow identifier. Sometimes, even when changed, the button in the SP List still works, sometimes it doesn't.