Another 'hidden' gotcha that I figured I'd share in the SharePoint / Power Automate world .... I created a Power Automate recently, which needed go through all items in a SharePoint list where a particular Checkbox field was ticked. Should be simple, right? Just put a wee Filter Query in the 'Get Items' action in Power Automate - easy, right? NO! I tried: CheckboxField eq true ❌ CheckboxField eq 'true' ❌ CheckboxField eq Yes ❌ sigh .... none of the above would work! In fact, the...

Recently I created a Flow to process items added to a SharePoint list as they are created. I needed each item to be processed on a 'round robin' basis, i.e., one at a time, to ensure an allocation algorithm worked fairly. I needed to prevent parallel runs of the Flow. However, in my testing, I was adding lots of items to the list at the same time, and I ended up with Flow runs with timestamps looking like this ... .... i.e., everything was being processed at the same time, and skewing my...

https://make.powerautomate.com/environments/@{workflow().tags.environmentName}/flows/@{workflow().name}/runs/@{workflow().run.name} Huh?! What does this do? Well it's surprisingly useful in the Flow World - I like to log all my Flow runs, so I know what's happening - really useful if you want to log what flows are doing what updates etc. The above code generates a URL which pulls in the Environment ID, Flow ID and Run ID - and allows you to go STRAIGHT to the Run Log for that Flow. Really...