Power Fx Formula Checker
Power Fx formulas can grow long, especially in OnSelect and OnVisible properties that mix If, Patch, ForAll and Notify. A single missing bracket, a curly quote copied from a chat message or a function written in the wrong case can stop the whole formula. This Power Fx formula checker scans your formula for structural mistakes and shows the line and column of each one, so you can fix it before you paste it into Power Apps Studio.
Also known as: power fx validator, power apps formula checker, power fx syntax checker, power apps formula error, check power fx online.
This checker looks at brackets, quotes, operators, function names and argument counts. It cannot see your controls, column names, data types or delegation limits, so Power Apps Studio remains the final check.
Your data is processed locally in your browser and is not uploaded to our servers.
Features
- Line and column for every issue
- Suggests the correct function name
- Checks argument counts for common functions
- Runs locally, your formula is not uploaded
How to use the Power Fx Formula Checker
- Copy the formula from Power Apps Studio, a blog post, a Teams message or a document.
- Paste it into the formula box.
- Click Check formula. Click Load broken example to see what the results look like.
- Read each issue. Errors are definite problems such as unclosed brackets, == instead of =, or the wrong number of arguments. Warnings are things to look at, such as a function name the checker does not know.
- Fix the formula and run the check again until the list is clear, then test it in Power Apps Studio.
Real-world use case: catching copy-paste mistakes before they reach your app
Most formula errors in real projects do not come from hard logic. They come from copying. A formula pasted from Word or Teams arrives with curly quotes. A snippet from a forum uses if() in lower case, but Power Fx function names are case-sensitive, so it must be If(). A developer used to another language writes Score == 50 out of habit, while Power Fx compares with a single equals sign.
Take a Submit button whose OnSelect should validate a form, patch a record and show a message. In a long formula, one missing closing bracket near the end can produce a red error far away from the real problem. Pasting the formula here points to the unclosed bracket and its line, and flags calls such as Notify() or Patch() that have too few arguments.
The checker is also useful in code reviews. When a colleague sends a formula for review, run it first to remove the mechanical errors, so the review can focus on logic, delegation and performance.
Know its limits. It does not know your control names, column names, data types or delegation limits, so a clean result does not guarantee that Power Apps Studio will accept the formula. It also expects English-style separators. If your Power Apps language uses semicolons between arguments, formulas will be reported as having the wrong number of arguments. Treat this tool as a fast first check, with Studio as the final judge.
Example input and output
Input: a formula with mistakes
if(Score == 50, “Pass”, Notify("Fail")Output from the checker
Error (line 1, column 3): Function names are case-sensitive. Use If instead of if. Error (line 1, column 3): The ( opened here is never closed. Error (line 1, column 10): Power Fx compares with a single =, not ==. Error (line 1, column 17): Curly quote found (often copied from Word or email). Use a straight quote instead. Error (line 1, column 22): Curly quote found (often copied from Word or email). Use a straight quote instead.
The corrected formula
If(Score = 50, "Pass", Notify("Fail"))Frequently asked questions
How do I find errors in a Power Fx formula?
Paste the formula into a Power Fx checker to find unclosed brackets, wrong quotes, wrong operators and incorrect argument counts. Then open it in Power Apps Studio, which also checks control names, data types and delegation.
Are Power Fx function names case-sensitive?
Yes. Write If, Filter and Patch exactly as documented. A lower-case if is not recognised, and the checker suggests the correct name.
Why does my formula use semicolons instead of commas?
Power Apps changes its separators with the language of your app or browser. Some regions use semicolons between arguments and double semicolons between formulas. This checker expects commas, so convert the separators first.
Why use PowerApps Ninja?
Your formulas often contain table names, internal URLs and business rules. PowerApps Ninja checks them locally in your browser and does not store or upload them. The checker is built for Power Fx and knows its common functions, which a generic code linter does not.