Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hi! All,
I've integrated Azure log analytics with Power BI and I've used the M-Query to create the report as well.
But, my question is around the below query. Seeing the results I was expecting user id against MdxQuery but I see Power BI Service and against DAXQuery I see the user ID. Can anyone explain the relevance of it and what's the design process behind it?
I understand that Power BI Service against Mdx Query might be by design, but do we've any more details about it?
PowerBIDatasetsWorkspace
| where LogAnalyticsCategory == "Query"
| distinct OperationDetailName, ExecutingUser
| sort by OperationDetailName desc
Solved! Go to Solution.
Checked internally with the PBI CAT team, this is kind of a bug, they'll plan to fix this. No eta as of now.
Checked internally with the PBI CAT team, this is kind of a bug, they'll plan to fix this. No eta as of now.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.