Forum Discussion
How does Merged Queries work in PBI Desktop?
Hi Mariusz apologies for delayed response, have not been able to get back to this until now.
You are correct - I have a step in the M Query to add a row to zStaging_CAP using the 'Table.InsertRows' function, this is where the native query folding failed. It looked something like this:
let
Source = LinkedTable,
#"Add Row" = Table.InsertRows(Source,0,({<Field Values>}))
in
#"Add Row"I'm not sure why this function made the query folding fail, but this was definately the reason and when I remove it the query folding is now fine. I will try to find another method to solve the problem (that doesn't break the query folding) and see if this has any effect on my original issue of it importing all the million of rows before doing the Inner join.
Thanks very much for your help.
Cheers,
Greg
Hi uberdube
Table.NestedJoin is supported by QF, so my guess is that the "zStaging_CAP" is braking it because of some reason.
1. Are both tables from the same SQL Server DB?
2. Can you see Native Query in "zStaging_CAP"?
Many Thanks
Mariusz
Hi Mariusz apologies for delayed response, have not been able to get back to this until now.
You are correct - I have a step in the M Query to add a row to zStaging_CAP using the 'Table.InsertRows' function, this is where the native query folding failed. It looked something like this:
let
Source = LinkedTable,
#"Add Row" = Table.InsertRows(Source,0,({<Field Values>}))
in
#"Add Row"
I'm not sure why this function made the query folding fail, but this was definately the reason and when I remove it the query folding is now fine. I will try to find another method to solve the problem (that doesn't break the query folding) and see if this has any effect on my original issue of it importing all the million of rows before doing the Inner join.
Thanks very much for your help.
Cheers,
Greg