Batch Operations and Throttling Mitigation in Power Automate
Bundle hundreds of SharePoint writes into a single $batch request to stop hitting throttling limits.
TAG
Common Questions
Some questions come up again and again, so I gathered them here in one place. This tag pulls together the practical answers I keep reaching for: whether Power Automate can run Python or PowerShell scripts, how to fix the changes conflict error in SharePoint, how to stop an infinite trigger loop, and how the "Parse JSON" action really behaves. You will also find function walkthroughs like the Excel "Count" function, the Power Apps "LookUp" function, and the Power Automate "isInt" function. Instead of theory, each article answers a specific question with a concrete fix you can apply right away. If you have hit one of these walls yourself, chances are the answer is already written down here, waiting for the next time it trips someone up.
Excel: Sum Function
Adds numbers, cells, or ranges into a single total. A single error in the range takes over the result.
Power Automate: isInt function
Checks if a string is an integer.
Add properties to SharePoint files
Add columns to library files so you can filter, sort, group, and find them by metadata instead of folders.
Excel: Count Function
Counts the cells in a range that contain numbers. Ignores text, blanks, and errors.
Power Automate: slice Function
Extracts a substring by position. Supports negative indices; endIndex is exclusive.
The reason it's EMail and not Email or email in Power Automate
Explains why SharePoint's email field is spelled EMail and why the casing breaks your filters
Power Apps: LookUp Function
Returns the first record that matches a condition, or a single reduced value. Blank if nothing matches.
How to stop an infinite trigger loop in Power Automate?
Stop a flow from re-triggering itself with trigger conditions, flag columns, or a create-only trigger.
The capital M that breaks your SharePoint Person column filter
How to fix the unexpectedly did not find the new dependency in the package graph
