This post is also available in: Deutsch

Change formatting of each individual value dynamically with Calculation Groups

This post is also available in: Deutsch In September last year I had already written an article on how to dynamically adjust the values of a measure, for example in millions, thousands or without scaling: Dynamic scaling of a measure in Power BI with DAX The approach at that time with the FORMAT function had a big disadvantage, the value is always converted to a text with FORMAT. This means that the measure can only be used in tables, because bar and line graphics cannot display texts. With old approach representation only possible in tables In the meantime, however, there is a much better way to display a measure with dynamic formatting using Calculation Groups. With Calculation Groups I can also create the formatting dynamically via DAX and this is – like every DAX function – calculated individually for each row. I use the same scenario as in the original article. If I have not selected any customers, I get high numbers and therefore I want to get scaling: However, if I filter on a specific customer, then the values should be displayed without scaling, because the scaling is too high in the normal case: Implement formatting via Calculation […]
This post is also available in: Deutsch Pretty much since I started the blog, I’ve been gradually sharing my code snippets for DAX and M here on the website. As the list got longer and longer and more and more confusing with all the examples, I decided to maintain and publish the code snippets on GitHub from now on. There I can provide and maintain them much more organized. As usual, I’ll add new examples to the list as I come across something that might be useful for you. The snippets are available on:: https://github.com/selimovd/PowerBISnippets/ […]
This post is also available in: Deutsch Last week I had investigated why a what-if parameter sometimes skips values and how to bypass this. In a discussion with my valued friend Bernat Agulló, we came across the topic of single values in slicers and he directed me to a tweet on how to do this with Tabular Editor. Single values as slicer with tabular editor In order to do this, the experimental features must first be activated in Tabular Editor. This can be done under File > Preferences: After that, the desired column must be selected. In the Metadata settings under “Extended Properties” a new “JsonExtendedProperty” has to be created: We specify ParameterMetadata as the name of the property and {“version”:0} as the value: Afterwards, the data model needs to be saved in the Tabular Editor and once we return to Power BI and drag the modified column into a slicer, we have the additional option to make it a “Singel Value” slicer: This is how the new slicer option can then be used: Conclusion I personally find the option to use a column as a single value slicer really amazing. However, one must be aware that there are […]
This post is also available in: Deutsch I like working pretty much with the what-if parameter in Power BI. With the help of this, it is possible to run through corresponding scenarios in a very fine-grained manner. What would my operating result look like if I can increase my sales by a factor of 2? How would it look with 1.5? And how about 2.35? I am aware that these increases are extremes. But with the what-if parameter, such evaluations go very easily with a single slider. Problem the what-if parameter does not work, the exact number cannot be set However, there is occasionally the case that exact values cannot be set. Let’s take the case just mentioned as an example. I would like to evaluate the development of my sales, accurate to 0.01 points. Accordingly, I create a what-if parameter: As range I would like to be able to select from -20 to 20 and the individual values should increase by 0.01 points: Now when I try to adjust the slicer of the what-if parameter to 1, 1.5 or 2.35 something strange happens, I don’t get the slicer set exactly to the value I want: Reason: Limitation to […]
This post is also available in: Deutsch Occasionally, as a Power BI developer, you are faced with the task of replacing the data source in existing reports with a published Power BI dataset. Especially if there are already several reports that were created with a copy of a PBIX file and are now to be consolidated to the same dataset. The question here is how best to proceed in order to achieve the goal as efficiently as possible. Delete the old data I had tried many approaches in the past, but the simplest one is by far the most efficient. I would like to demonstrate this using the example of my vaccination statistics, where I access the dataset of the German report for the English version. Still I would like to take the visualization as a basis from the original report. In the first step we need to delete the existing data. This sounds brutal at first, but trust me, the individual visuals will work again later when all tables, columns and measures are named identically. 1) So in the first step, we delete all the tables created by DAX, including the Measure table, directly in Power BI: 2) […]

Follow me on LinkedIn and you’ll gain access to valuable insights, expert tips, and industry updates related to Power BI. Stay ahead of the curve and supercharge your analytics skills today!

Supercharge your Power BI skills!