So came across a really weird series of issues recently when creating SharePoint fields that I figured I'd share. I created a set of simple text fields for use in a SharePoint Lookup List with 8,000+ rows. Adhering to my 'KISS' (Keep It Simple, Stoopid) principle, I created each field with initial Display Names of ICL1, ICL2, ICL3 and so on. Ugly, yes, but my aim was to create the fields with simple Internal Names of ICL1, ICL2 etc, that I could then change the Display Names of to something...

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...