Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredJoin us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM. Register now.
I have a published dataset that contains both 'Direct Query' mode tables and 'Import' mode tables. In desktop, I have created a thin report connecting to the published dataset. The thin report, returns data from both types of table.
When I create Measures that reference my Import mode tables, all is good.
When I create Measures that reference my 'Direct Query' mode tables I recieve the following error:
{"error":{"code":"DM_GWPipeline_Gateway_ImpersonationError","pbi.error":{"code":"DM_GWPipeline_Gateway_ImpersonationError","parameters":{},"details":[],"exceptionCulprit":1}}}
If I switch my 'Direct Query' table to an 'Import' table, the measures resolve as expected. Has anyone experienced this issue? Regards, Steven
Hi @Anonymous ,
Is there any update?
Best Regards,
Dedmon Dai
Hi @Anonymous ,
There are some dax functions don't support in Direct Query model. Would you please refer to https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2012/hh213006(v=sql.110)?redirectedfrom=MSDN#functions-not-supported-in-directquery-mode for these function.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Best Regards,
Dedmon Dai
Hi Dedmon Dai,
Thanks for your reply and advice. This is something that I should keep in mind for future reference as I'm certain that we currently use some of those listed functions; however, I do not believe this is the underlying issue.
I have further identified that the issue occurs on any Direct Query mode fields; it is not limited to DAX Measures as I thought previously.
I'm current working through the issue with Microsoft and we are focussing on the Gateway as the source of the problem.
I'll keep you posted on our developments.
Regards, Steven