Measures as legend in Azure Maps

[Anonymous]

Can someone help me understand technically why it is not possible to use a measure in the legend field of an Azure map but instead use a calculated column?
(In some cases calculated columns give different values as compared to a measure despite building similar logic) So in such cases where measure is our only option, what should we do.

[Anonymous · Accepted solution]

Hi @Anonymous ,

Thanks for reaching out to our community.

Not only can't you put measures in the Legend of Azure Map, but you can't put measures as long as it's the Legend in the visual, such as Stacked column chart.

In Power BI, measures and calculated columns serve different purposes, which is why you can’t use a measure in the legend field of visuals. Here’s the explanation:

Measures are dynamic calculations that are evaluated based on the context of the data in your report. They are typically used in the Values area of visualizations to perform calculations on the fly. However, because measures are context-dependent, they can’t be used in fields like Axis or Legend, which require static values.
Calculated Columns are static and are computed when the data is loaded or refreshed. They can be used in any field, including Axis and Legend, because their values are fixed and do not change based on the context of the report.
When you encounter situations where calculated columns give different values compared to measures, it usually stems from the context in which they are evaluated. Measures are evaluated in the context of the entire report, while calculated columns are evaluated row by row when the data is loaded.

Note that this is moible apss forum. The next time you encounter as issue from Power BI Desktop, please go to the Desktop forum to ask questions. Going to the right forum to ask questions can do more with less.

Best Regards,

Stephen Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.