Direct Query behaviour different in Service vs Desktop

[matthewcornish5]

Hi All

Not sure if this is a bug/limitation but what I am seeing is, when in Desktop I have a query that does in essence SELECT * FROM A_View. With no where clause this is about 45M rows. This dataset is accessed when doing a drillthrough to another page.

When I do a drillthrough I can see in SSMS that i get a query come in with a where clause limiting it down to what I am looking at and works fine.

When I upload to the service and do the same, I get the original SELECT * FROM A_View without a where clause.

Is there a setting or something I am missing?

[SaiTejaTalasila]

Hi @matthewcornish5 ,

Are you getting the expected values as output after performing drillthrough on power bi service report?

As they are designed for different purposes they system design might be different and execution plan generated will be different.

Thanks,

Sai Teja 

[v-fenling-msft]

Thanks for lbendlin's concern about this issue.

Hi, @matthewcornish5 

I am glad to help you.

May I ask if the result of your drill through operation in Power BI Service is the same as the result of your drill through operation in Power BI Desktop?

Have you made any other settings such as permissions in Power BI service? Sometimes, Service may not have the same permissions as your Desktop and the query behavior is different.

I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Fen Ling,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[lbendlin]

DAX Visual queries employ paging (usually TOPN(501,...) - you can check in Performance Analyzer).  Can you provide some more details on your specific setup?

[matthewcornish5]

This is the query that gets sent when using desktop

Query sent from Desktop

This is what gets sent by the service

Query sent from Service

Both had the exact same information clicked on, a drillthrough on ParentID. Top one brings back 5 rows of data, bottom one is about 45M rows (which it obviously falls over with)

[lbendlin]

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .