Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hi, I'm getting an error message which says the following (I'm attaching a screenshot of the message), It basically appears when i try to visualize the result of a visual query in datamart, The query contains a group by and a merage of two tabelles, I wonder if it ever happened with you before? and how i can slove that issure? I appreciate any help
Solved! Go to Solution.
Hi @Anonymous ,
It looks like your M query isn't fully foldable to the SQL source. When I say 'foldable', I mean that you've used some M code that does not have a direct translation to SQL code. For example:
-- Table.RemoveColumns can be translated via the SQL SELECT clause
-- Table.SelectRows can usually be translated via the WHERE clause, sometimes not
-- Table.Group can be translated via the GROUP BY clause
-- Text.Trim can be translated to RTRIM(LTRIM(..))
-- Table.TransformColumnTypes can usually be translated to CONVERT(<data type>, [Column]), sometimes not (change type to integer, for example)
-- Table.SplitColumn can NOT be translated as there's no equivalent SQL function
-- Etc.
You can check whether your M code folds to the source at each step by right-clicking on the query step and seeing if 'View Native Query' is greyed-out or not. Black/selectable = folding, greyed-out = not folding.
Good info here:
https://www.biconnector.com/blog/query-folding-power-bi-everything-you-need-to-know/
Pete
Proud to be a Datanaut!
Thanks a lot Pete for the help. I have a better understanding of the issure and I'll work on solving it.
Hi @Anonymous ,
It looks like your M query isn't fully foldable to the SQL source. When I say 'foldable', I mean that you've used some M code that does not have a direct translation to SQL code. For example:
-- Table.RemoveColumns can be translated via the SQL SELECT clause
-- Table.SelectRows can usually be translated via the WHERE clause, sometimes not
-- Table.Group can be translated via the GROUP BY clause
-- Text.Trim can be translated to RTRIM(LTRIM(..))
-- Table.TransformColumnTypes can usually be translated to CONVERT(<data type>, [Column]), sometimes not (change type to integer, for example)
-- Table.SplitColumn can NOT be translated as there's no equivalent SQL function
-- Etc.
You can check whether your M code folds to the source at each step by right-clicking on the query step and seeing if 'View Native Query' is greyed-out or not. Black/selectable = folding, greyed-out = not folding.
Good info here:
https://www.biconnector.com/blog/query-folding-power-bi-everything-you-need-to-know/
Pete
Proud to be a Datanaut!
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
15 | |
11 | |
8 | |
8 | |
7 |
User | Count |
---|---|
15 | |
13 | |
9 | |
6 | |
6 |