Custom M function applied row by row
"Custom M function applied row by row" is one of the performance checks Auditabi runs on a Power BI semantic model. n query(ies) call a custom function inside Table.AddColumn or Table.TransformColumns. It is a low-severity finding: hygiene and maintainability, worth fixing when you next touch the object. Express the transformation with native operations, or push it into the source.
What is detected
n query(ies) call a custom function inside Table.AddColumn or Table.TransformColumns. Custom functions never fold and are evaluated once per row in the mashup engine.
Why it matters
Hygiene and maintainability. Fix when touching the object.
How to fix it
Express the transformation with native operations, or push it into the source.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.