After struggling with conditions based on SharePoint list item metadata I stumbled upon the "Run a custom action when a SharePoint list item is modified" - this template changed a yes/no value to bool expression after saving. eg "Approved" is equal to "No" would become "Approved" is equal to "bool:false" my flow was running smoothly. I've tried to recreate the flow for a production environment and the flow template seems to have disappeared and I cannot replicate the condition.
Stanger still when attempting to add a yes/no field in a condition I am no longer presented with a drop down for Yes/No/Custom Value, it only gives me free text - in workflows where I have this condition available, the condition is displayed in advanced mode with the following string
@equals(body('Get_item')?['Approved'], bool('false'))
Have I missed any significant rollout??
Solved! Go to Solution.
Hi @Anonymous,
This should be related with the condition UI.
Besides, would you please share a screenshot of the "Approved" is equal to "No" situation?
Sometimes the Yes or No text Input may not working as expected, and Flow would convert the Yes or No selection into the corresponding boolean value.
If the condition works as expected, then you should be good to go.
Besides, Microsoft Flow would stay in Updating the Flow design UI, so there may be more changes on this part.
And if you have any better idea, please consider submit it under Microsoft Flow idea forum:
https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas
Regards,
Michael
Hi @Anonymous,
This should be related with the condition UI.
Besides, would you please share a screenshot of the "Approved" is equal to "No" situation?
Sometimes the Yes or No text Input may not working as expected, and Flow would convert the Yes or No selection into the corresponding boolean value.
If the condition works as expected, then you should be good to go.
Besides, Microsoft Flow would stay in Updating the Flow design UI, so there may be more changes on this part.
And if you have any better idea, please consider submit it under Microsoft Flow idea forum:
https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas
Regards,
Michael
Hi Michael,
This won't work for any new workflow however I managed to convert an old workflow where Flow converted the Yes or No selection into the corresponding boolean value and this works a treat. Unfortunately any new workflow started from a blank template still refuses to work.
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!
User | Count |
---|---|
44 | |
42 | |
37 | |
36 | |
23 |
User | Count |
---|---|
41 | |
39 | |
30 | |
29 | |
29 |