DAX measures as defined in semantic model (dataset) not visible in reports based on LIVE connection?

[BBrak]

As far as I can see, DAX measures that are defined in a given semantic model are not visible in Power BI reports that are based on a LIVE connection to that semantic model. It would be nice if the DAX measure could be displayed even if it couldn't (and shouldn't) be edited.

Is there currently a workaround for this, or has this been requested already?

Tnx!

[danextian]

Hi @BBrak 

It is not possible to view the measure definition of a live connection report to a semantic model except, of course, for those thave been created in the report itself.  The measure definitions though can be viewed using the XMLA endpoint of  a workspace using Tabular Editor. The catch: XMLA endpoint is for Power BI Premium, Premium Per User, and Power BI Embedded workspaces only.

[Deku]

You can enter the measure definition in it's description, in the source model, so it appears on hover in the report.

You can also use Dax query query and run

Evaluate

Info.measures()

[BBrak]

hi @Deku, thanks for your suggestions. Adding the measure definition to the description works technically, but many of my DAX measures are so long that it becomes basically unreadable.

When testing your second suggestion I ran into a permission issue even though I'm signed in and have access to the dataset in question. Any idea why this might be occurring despite that?

[Deku]

It might not be possible since it is a remote model

[BBrak]

I have found a workaround, not ideal, but this works best for me now. I run the following code in DAX Query View, then copy + paste in Power Query as a table in my data model.

EVALUATE

SELECTCOLUMNS(

    Info.Measures(),

    "Measure Name", [Name],

    "Data Type", [DataType],

    "Expression", [Expression],

    "FormatString", [FormatString],

    "DisplayFolder", [DisplayFolder]

)

Thanks for the original suggestion.

[v-aatheeque]

Hi @BBrak ,

Thank you so much for the update ,we’re glad to hear the issue has been resolved on your end! We really appreciate your time and effort in closing the loop.

If any of the replies in this thread helped along the way, please consider marking the most relevant one as the accepted solution. This helps others in the community who may face similar challenges to find answers more efficiently.Also, feel free to share your own solution in the thread it would be valuable for others who might benefit from your experience.

Thank you again for your kind cooperation and contribution to the community!

[Anonymous]

Hi @BBrak 

Glad to hear you solved the problem yourself! Could you please Accept your method as Solution? This will help more users who are facing the same or similar difficulties. Thank you!

Best Regards,
Yulia Xu