Drill through from card visual in Power BI

A common reporting requirement is to drill through from a high level dashboard to a detailed page and Power BI does support this with the drill through feature as described here. However, as of this writing, drill through from a card visual is not natively supported. This post explains how to work around this limitation.


The trick is to stack another visual which has native support for drill through on top of the card and make it invisible so the end result looks like you drill through from the card visual. 100% stacked bar chart is good candidate for this. The bar chart in below (1) is a 100% stacked bar chart as can be seen in 2. You need to turn off the background (3) and filter it to the same dimension value (4) as your card visual. Now stack it on top of your card.

Next you will need to make the bar transparent. Create a measure (1) and the formula is shown below 2 (the two trailing 0 means 100% transparent) and then clicking the Fx button under data colors card (3).

Once the Default color – Data colors window opens, set it as below. You will need to use the measure you created before for the transparent color (below 1). Now your 100% stacked bar chart should be invisible and when you right click you should see the drill through selection in the menu.

Before I wrap up, another pro tip is if you have lots of card visual on your dashboard page, make sure you name everything properly, it will save you tons of time later on if you need to find an item and make some changes.

not properly named
properly named


Conditional formatting at different hierarchy level in Power BI

Recently I have a request to only show conditional formatting when users drill down to a particular level of hierarchy.

Using AdventureWorks sample data, I have a product hierarchy (Category > Subcategory > Model > Product) on rows, fiscal year on columns and sales qty in values in a matrix visual.

I have applied conditional formatting as below and you can see in the GIF above that conditional formatting is applied at all levels of the hierarchy.

But my requirement is to only show conditional formatting when users drill down to model level or below. What that means is I don’t want to see conditional formatting applied if users are at category or subcategory level. Let’s have a look at what the final result is before I talk about how to do it.

To achieve this, you need a separate measure to use in the Base on field drop down (See 1 below, in the previous screenshot I have used Order Qty). Also in the Default formatting make sure you select Don’t format (See 2 below). I will explain why in the next section.

The definition of the measure Order Qty Conditional Formatting is

It uses ISFILTERED to check if there is a direct filter coming from model or product column in the Product table. Return the Order Qty value if it’s true, or return blank. When users don’t drill down to model or product hierarchy level, this measure always returns blank. What the Default formatting option does is to let you decide how to format blank values. In my case, I don’t want to format it, hence the Don’t format selection in the drop down.

There you have it. If there is another way to do this, please share with me in the comments below. Happy weekend!

How to reference ‘&’ in Power BI URL Parameters

I recently helped one of my colleagues to set up some hyperlinks using Power BI service URL parameters to direct users to a specific page of our report with some filters applied in advance. If you haven’t heard of this feature, here is the official doc https://docs.microsoft.com/en-us/power-bi/collaborate-share/service-url-filters.

When I tried to use this xxxxxxxxxxxxxxxx?filter=Store/Region eq ‘South & West’ (xxx… is the unique URL for one page of my report), it didn’t work. In the official doc it doesn’t mention how to reference ‘&’ as you can see from below screenshot. I hope someone from Microsoft can update this soon.

It turns out that you need to use %26 in place of &, so in my case the correct URL should be

xxxxxxxxxxxxxxxx?filter=Store/Region eq ‘South %26 West’.

Before I close off, one more advice is to edit your URL in notepad+.

Thoughts on Calculated Columns in Microsoft Power BI/Excel Power Pivot/SSAS

I remember a renowned BI professional once said don’t create calculated columns unless you need it for slicing and dicing. I largely agree with this but there are cases that calculated columns are needed to make your DAX formula easier to understand.

An over simplified example is if I want to do a sum of sales amount for special products only, I could do this without below highlighted calculated column with this DAX formula

Sales Amount Special Product =
SUMX ( Sales, Sales[Net Price] * Sales[Quantity] ),
FILTER ( ‘Product’, RIGHT ( ‘Product'[Product Code], 1 ) * 1 = 6 )


But If I take advantage of it my formula would be:

Sales Amount Special Product =
SUMX ( Sales, Sales[Net Price] * Sales[Quantity] ),
‘Product'[Special Products] = TRUE ()

Athough it’s simpler but in this instance my suggestion is not to add special products to your product table.

But what happens if your business logic is way too complex? If you code all logic in one monster DAX formula, it would soon become harder to understand by your team members during your absence and even you will have trouble when go back to the same PBIX file after a period of time. In this situation, it might be helpful to use claculated columns to make your fomula more understandable. Well, one could argue that you can add comment in your fomula for some explanation but most of times you don’t document enough or you are under a tight schedule to do so.

Another consideration is if part of your business logic is also needed in many other DAX formulae, then it’s sensible to add it as a calculated column so it can be reused in many different places. You can use variables inside one DAX formula if you need to reuse the same logic multiple times. However, DAX currently don’t support global variables and I am not sure if it will in the future. For now, calculated column is your only option when you need to reference the same logic many times in different DAX formulae.

I have worked on many very complex Power BI models (50+ tables and very complex business logic) and I often see people create many calculated columns as intermediate steps to support other DAX fomulae. There is a fine balance here. Too many calculated columns would make your table hard to browse and potentially increase your model size exponentially if too many unique values inside those calculated columns. On the other hand, if you create monster DAX formula it could also create maintainability issue. So you should really give it a careful thought where to draw the lines.

Next question is where you should create those calculated columns? You can use DAX but you can also add them inside Power Query with M language. Best practice is you should add all additional columns or derived columns inside Power Query as part of ETL/ELT process. You only use DAX if you can’t write a M expression to do the same thing.

Well, the final point I want to make is if your company has a data warehouse team to support reporting function then you should push all those logic for additional columns to the database team and let them create them as part of ETL/ELT process. In doing so, the same logic can be applied to other reports and beneficial to other reporting teams if there are more than one in your organisation. I know it’s a time consuming process to make structural changes to data warehouse in a production environment so you should keep some level of business logic inside your model, especially the ones that are likely to have multiple rounds of changes in the near future.

Well, before I wrap up, I want to point out that depending on your company environment, if you don’t get enough support from backend database team, you have data flows and promoted/certified datasets as another options to share the same business logic with your co-works.  Power BI is powerful and flexible enough to empower you in many different ways so I hope you find the best solution for your organisational reporting needs.


It’s been a while since my last post. I have been busy for the past a couple of months. I have gained my MCSE certification for data management and analytics. I am happy that I didn’t wait any longer as Microsoft just recently announced retirement of many certification path until 30 Jun 2020, which means you have roughly 4 months time to achieve your certification title if you are only 1 or 2 exams away. Alternatively you can wait until the new certification path arrives which will be role based. You can find the official announcement here.

Another thing I did since my last post back in Nov 2019 is I had my first Power BI user group talk. It’s a great experience to share something I learned with the Power BI community here in Sydney Australia. Will I do it again? Oh yeah, I even want to be a speaker at one of the Microsoft conference one day.

Ok, enough of this. Let’s get back to the main theme of this post. Chapter 11 is all about AI capability in Power BI desktop. I talked about some of the AI capabilities in my previous post here. This chapter covers many other aspects of AI in Power BI desktop such as how to do liner regression with DAX expression, how to run R script inside Power BI desktop and create R visuals and use Azure machine learning inside Power Query to extract key phrase etc. I won’t dive into details as it’s a lot to cover in one post. I will leave it to you to read it yourself.

Alternatively you can find lots of additional info about AI capability in Power BI on Power BI official blog here.



This post is a follow up on my previous post of Sentiment Analysis in Power BI Desktop. In Power BI Nov updates, some AI transformation capabilities have been added to Power Query including sentiment analysis which is part of Text Analytics. You will see the AI Transforms in Power Query Home ribbon.

AI Transform

If you don’t see it, you need to enable it by going to File, Options and settings, Options and then tick the box for AI insights function browser. The Learn more hyperlink has not been updated to take you to relevant page as of this writing. It will take you to Microsoft main page instead, I hope this will be rectified soon. preview feature.PNG

To use these new AI features, you need to have access to a premium capacity backed workspace. If you don’t and clicked Text Analytics for example, you will see below error message.

error message for no premium capacity

If you do, this is what you will see. Select Score sentiment in the left navigation pane for Text Analytics and in the Text drop-down select the text column (Comment field is the one in my sample data) you want to do sentiment analysis and click OK.

ai with premium capacity

A Score sentiment column has been added to give you the score for each text value in Comment column. Also notice that behind the scene, a Score sentiment function has been added.


If you look at the M code generated for the Table query, a M function named AIFunctions.PostProcess has been called to give you the output of Score sentiment column.

M code

As of this writing, Power Query M function reference has not been updated yet so I can’t find any reference there.


However if you paste below M code in a blank M query, you will see all AI functions reference in Power Query and if you click the blank space in column Value for the first row, you will see the definition for AIFunctions.PostProces.

Source = #shared,
#”Converted to Table” = Record.ToTable(Source),
#”Filtered Rows” = Table.SelectRows(#”Converted to Table”, each ([Name] = “AIFunctions.Capacities” or [Name] = “AIFunctions.Contents” or [Name] = “AIFunctions.ExecuteInternal” or [Name] = “AIFunctions.GetAutoMLEntity” or [Name] = “AIFunctions.PostProcess”))
#”Filtered Rows”


If you have read my previous post, you will see that performing Text Analytics in the latest Power BI desktop is a lot easier if you have access to a premium workspace. When you publish your PBIX file, you will need to publish it to a premium workspace as well so it will continue to work in Power BI service.

Sentiment Analysis in Power BI Desktop

Edit: It’s not a very intuitive process to do sentiment analysis in Power Query. Good news is that from sometime next week text analytics will be accessible directly from Power BI Desktop. Read below for the announcement from Microsoft or you can read my new post to see how this works in Power BI November updates.


In my last post of book review, the author demonstrated how to use dataflow AI capability for sentiment analysis, but that’s a premium workspace feature. In this post I will show you how you can do sentiment analysis in Power BI desktop.

1. You need to have a Azure subscription. It’s free to sign up and you will also get bonus $280 credit to use Azure services for 30 days.


2. Log into Azure portal and click All resource in the left pane and click Add.


3. Search Text Analytics and click Create


4. Fill required fields and click Create. Note that I have selected the free F0 pricing tier.


5. Once deployed, click on Keys in the left navigation pane and you will see 2 keys. We will need one of them later. 8

6. To keep this demo simple, I have copied some restaurant review for a place near my office and I have added index column as id. All done in Power Query with a couple of clicks. You need to ensure that text column doesn’t contain empty values and id column doesn’t have duplicates. Also if your id and text columns have different names, rename them to id and text respectively or the Text Analytics will not work.



7. Now rename your query to Message. In the Queries pane right click on the Message query and select Reference, then right click on the newly generated query Message (2) and rename it to SentimentAnalysis.


8. With the SentimentAnalysis query selected in the queries pane, click on the fx button in the fomula bar, you will see a new step called Custom1 added in the Applied Steps pane.


9. Change the fomula to below and you will notice a Json file has been created. This is required because the Text Analytic API needs Json file as input and it will also output Json file later in the steps which we can easily convert to table format with Power Query.10.PNG

10. Copy one of the Keys from step 5 and create a new Power Query parameter, name it APIKey or something you like and paste the key in Current Value and click OK.



11. Click fx in the formula bar and a new step Custom2 will be created and then replace the M formula with below formula (replace the red text with name from step 4). At this point you will see a Json output has been returned from the API call.

= Web.Contents(“https://textanalysis-demo.cognitiveservices.azure.com/text/analytics/v2.1/sentiment”, [Headers=[#”Ocp-Apim-Subscription-Key”=APIKey], Content=Custom1])


12. Double click the Json icon you will see a record with the documents and errors fields and with List objects as values.



13. Select the List object of the documents field and then click To Table to convert the list to a table.15.PNG

14. Leave the To Table window as is and select OK.


15. Click the expand button, uncheck the Use original column name as prefix then click OK.


16. Now you will see the id of the text and score returned by the API call. Change the data type for id column to Whole Number by right clicking on id column and select Change Type then finally select Whole Number data type. What’s missing at this point is the text field which we can bring back easily with Merge Queries feature in Power Query.


17. With the sentimentAnalysis query selected in the query pane, click Merge Queries button in the Combine section of Home ribbon. When you see the Merge window, select the Message query from the drop down and make sure id column in both tables are selected then click OK.


18. Click the Expand button, uncheck id and click OK.


19. Now you will see the text along with id and score.


P.S. With the free pricing tier, you can only make 5,000 API calls for free. So don’t not make excessive API calls. Also limit each message under 5,000 characters to avoid any errors and pass less than 1,000 rows of text per API call. Please also disable Power Query background data refresh or you will reach the limit very quickly if you need to do some serious text analytics.


You can download the sample file here. You need enter your own Azure Text Analytics service Key to be able to use the file.


Chapter 10 covers some of the Artificial Intelligence (AI) capabilities in Power BI Service and Power BI desktop. The author showcased how to set up sentiment analysis and image tagging in Power BI dataflow. Dataflows, along with Dashboards, Reports, Workbooks and Datasets are artifacts of Power BI workspace. However, AI features of dataflow only works with Power BI workspace in premium capacity.


If you try to use AI feature of dataflow in workspaces not backed by premium capacity, you will get below error.


In chapter 10, the author also introduced Key Influencer visual in Power BI desktop. This is the first visual released by the AI team in Power BI. You can watch some demo videos from Guy in a cube YouTube channel here and another one form Power BI YouTube channel here.

In my next post I will walk you through how to set up sentiment analysis in Power BI desktop if you don’t have access to Power BI premium workspace.


Chapter 8 is introduction for DAX and it covers all the basics about DAX which includes:

  • Calculated Columns
  • Measures
  • Calculated Tables
  • Calculate Function (the most important DAX function)
  • Variables
  • Time Intelligence Functions

It’s a good start for beginners. If you already have working knowledge about DAX, you may want to skip this chapter. If you want to learn more about DAX, I highly recommend Marco Russo and Alberto Ferrari’s book here .


Chapter 9 talks about the difference and similarities between Excel and Power BI. Excel, as part of Office 365, has a built-in add in called Power Pivot, together with Power Query and Power Map enable business analyst to create BI models right inside Excel. Before we had Power BI desktop, that’s how business people create self service BI reports in Excel and share those reports with end users on SharePoint on premise. Power BI, on the other hand, is another (the preferred) way of creating BI reports in Power BI desktop and share reports online by publishing your model to the cloud. (You can also share Power BI reports locally with Power BI Report Server). I started building Power Pivot models back in 2010 so Excel BI always has a place in my heart 😊.

Both Excel and Power BI use the same engine behind the scenes. They are actually SQL Server Analysis Service Tabular model (SSAS Tabular) running on your local machine. Once you master either Excel or Power BI, it’s an easy transition to build larger data model in SQL Server Analysis Service. By the way, if you master both of them, you may consider getting certified for MCSA: BI Reporting.




Find Strings of One Column in Another

I came across a very interesting problem recently. I want to find out whether the text string in one column exists in another. Take the first row for example, I want to see if the string (‘Apple Pie’) in column 1 actually contains the string (‘pie’) in column 2.


I always thought that DAX function SEARCH and FIND are used to find a fixed text string in one column, like below,


However, when I tried below, it also worked. Happily surprised 😊. FIND returns error here because it does case sensitive search. Even you only have one row returns error, the whole column will return error, very disappointing!


Then I started wondering whether DAX has other functions that can do the same thing? Sure it does. CONTAINSSTRING and CONTAINSSTRINGEXACT do just that, but you need to switch the column sequence here where the first parameter is the ‘Within Text’ (‘Find Text’ is the first parameter for SEARCH and FIND). CONTAINSSTRINGEXACT is case sensitive, but it doesn’t return error like FIND does.

So, you know which function you should use in the future. CONTAINSSTRINGEXACT wins over FIND for case sensitive search.


Can you use these 2 functions to find fixed text string? oh yeah!



Some folks like to do things in Power Query and it’s actually best practice that you should add custom columns in Power Query with M functions whenever possible. So let’s see how we can do this with M. Text.Contains function does the same thing here, but it also has the optional third parameter for case insensitive search. Leave it out if you want to do case sensitive search.


In summary, if you want to find out if text string in one column exists in another, you should do it with M as it’s more flexible and best practice to do so. Only use DAX calculated column when you can’t achieve what you want to do with M.