Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I am running DMVs against datsets in our Premium PowerBI Service. I was interested in analysing and documenting the M-Code behind the PowerQuery queries so I ran the following query in SSMS. This connected to a dataset called "Timesheet" behind a PowerBI file of the same name.
Select *FROM $System.DISCOVER_M_expressions
I get a single row result back called "Agile CC" (see below).
I assumed this result meant there is only one M-Query (M-Expression) - called "Agile CC" in this dataset behind my "Timesheet" PowerBI report. However, when I download the PowerBI file, it is clear there are many queries (25 based on the view below) in the report/dataset. For each of these queries I can see M-Code behind them (for example the "EDW Calendar WorkDate query" see below) , that isn't returned or visible from the results of the"DISCOVER_M_EXPRESSIONS" query.
Can someone explain why I see more M-Code in the PowerBI file, than I can from the M_EXPRESSIONS query?
Thanks in Advance
Steve
example of query visible in the advanced editor of the PBI file, but not in the results of the DMV
Articles I have reviewed trying to understand this.
@https://blog.crossjoin.co.uk/2019/05/08/extract-m-code-dmv/
@https://medium.com/@martijnlentink/automate-your-power-bi-documentation-33951525c381
I'm seeing no data returned from this DMV. Nothing.
@Anonymous , I can see error, and it is asking for edit credentials. can check that
refer how to handle error in power query
https://www.youtube.com/watch?v=OE6DPmKqN7s
https://www.youtube.com/watch?v=9-Lag0VOiTs
debug issue
https://www.youtube.com/watch?v=OE6DPmKqN7s
@amitchandak I have double checked this (by replicating the issue on a new PBI dataset in premium workspace), and it turns out credentials are not the problem.
Regards Steve
Did you ever resolve this issue? I am seeing the same behavior.