Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
Anonymous
Not applicable

Error with visual query visualizations

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

Skärmklipp.PNG

 
1 ACCEPTED SOLUTION
BA_Pete
Super User
Super User

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



Now accepting Kudos! If my post helped you, why not give it a thumbs-up?

Proud to be a Datanaut!




View solution in original post

2 REPLIES 2
Anonymous
Not applicable

Thanks a lot Pete for the help. I have a better understanding of the issure and I'll work on solving it.

BA_Pete
Super User
Super User

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



Now accepting Kudos! If my post helped you, why not give it a thumbs-up?

Proud to be a Datanaut!




Helpful resources

Announcements
July 2025 community update carousel

Fabric Community Update - July 2025

Find out what's new and trending in the Fabric community.

July PBI25 Carousel

Power BI Monthly Update - July 2025

Check out the July 2025 Power BI update to learn about new features.

Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

Top Solution Authors