Why you should avoid Implicit Measures in your Power BI model

  • Changing the default summarization doesn't suddenly change all the visuals, but I do agree it's better to use explicit measures for anything other than trivial or off the cuff projects.

  • This was removed by the editor as SPAM

  • This was removed by the editor as SPAM

  • I completely agree with you; a key benefit is the ability to use the Analyze in Excel feature. This is particularly useful if your Power BI audience includes accountants who may not be as interested in visualizations but are keen on generating Excel Pivot Tables from your data model.

    A small issue with this method is the naming of your measures. For instance, if there's a field named 'amount,' you cannot have a measure with the same name in that table. I address this by renaming the field to something like '_amount' and hiding it, allowing me to then create a measure called 'amount.' I make these changes not in Power Query but in the SQL view that Power Query accesses. My preference for avoiding renaming in Power Query is a subject for another conversation.

  • Comments posted to this topic are about the item Why you should avoid Implicit Measures in your Power BI model

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

Viewing 0 posts

You must be logged in to reply to this topic. Login to reply