Forum Discussion
Difference between the two logs generated by PowerBi.
The first one can come from a developer working in Power Query editor, the second one from the dataset. What problem are you trying to solve?
Hi Ibendlin,
I have designed a custom connector which supports native query, now I would like to add support for limit clause. I have done changes refering to this Parameters for the Odbc.DataSource function - Power Query | Microsoft Learn but I still dont see the Limit clause getting appended to the query I pass.
AstVisitor = [
LimitClause = (skip,take) =>
if (skip > 0) then error "Skip/Offset not supported"
else
[
Text = Text.Format("LIMIT #{0}", {take}),
Location = "AfterQuerySpecification"
]
],
I was going through the logs, at first the query got appened with limit, later it didnt.
FYI:
I havent made any code changes further.
We have cleared cache as well.
Under --> Options -->Global --> Data Load
At first, limit clause got appened with the query we pass. But later on, it didnt behave as expected.Could you suggest any changes that needs to be done in power query (.pq) file.
Regards,
Sushma
I am not aware of a way to tell Power Query not to use the cache. Maybe set the cache size to zero?
Yes, I tried that. It didnt work either.
But could you suggest, how do we actually desgin a custom connector which supports limit under native query.