Report Level Measures Data Type to default based on return value

Currently, when creating report level measures on live dataset connections, the measure's data type always defaults to Number, even when the return value is clearly text. In my experience, many of my report level measures are actually text values I'm using for conditional formatting or titles, if I'm creating a numeric measure I do this in the original dataset most of the time as it's usually something helpful for every report, whereas the text measures are typically more report specific.


Would be great if the default formatting behaved the same as normal measures (ie base on the return value).

New
Comments
Joel_Miller2
New Member

Interesting idea. I've voted for it because I would like Microsoft to look more closely at the user experience when creating report-level measures. Evidently, this defaulting of report-level measures to the Decimal Number / Double data type does cause a bit of confusion. See this Idea: https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=e79a9593-09d7-ee11-a73e-00224855381e


I think the reason that thin (live connected) reports require report-level measures to have their data type set explicitly, is that it is unable to reliably infer expression data types without direct access to a local model and all of the column data types. Hopefully in the future, thin reports will be able to get more information about the remote model to make this possible.

Joel_Miller2
New Member

https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=e79a9593-09d7-ee11-a73e-00224855381e

Joel_Miller2
New Member

Because the link in my previous comment doesn't seem to be working. Here it is:


Allow use of report-level measures for conditional formatting


https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=e79a9593-09d7-ee11-a73e-00224855381e

fbcideas_migusr
New Member
Status changed to: New