Fabric is Generally Available. Browse Fabric Presentations. Work towards your Fabric certification with the Cloud Skills Challenge.
Hello,
I have basically two tables, the first one looks like this:
Product A | Cat A | 100 EUR |
Product B | Cat A | 80 EUR |
Product C | Cat B | 60 EUR |
The second table one holds min, max and average values per category for all products. Let's call this aggregations table (I have done this in KNIME, as it is way easier, than doing lots and lots of calculated measures in PBI).
In the Model view I have related both tables with a many : one cardinality going from the above product table to my aggregations table.
I also have a slicer on the categories, so users can select if they want to see products (and aggregations) for Cat A, Cat B etc.
I basically want to display the above products table and show for example the avg price in a card per category (! important) above it.
However, when I draw the avg Cat A onto a card it summarizes it. I don't want a summary or any kind of aggregation. I simply want to show this to my users so they can make a comparison to see how much the current product price is above or below the avg product price for that category.
Is there any way to display a simple number which is filtered by the selection in the slicer?
Solved! Go to Solution.
I am really surprised that there seems to be absolutely NO visual to represent a single value like a product price without any aggregation. It feels like I am missing a crucial part here or is that requirement sooo exotic?
Edit: Now I found the solution. So for anyone who is interested: the problem was that the category I mentioned above was also present in another table. I connected both in the data table and took the slicer with data from that other table. Now I have changed to the original pricing table and voilà it works!
I am really surprised that there seems to be absolutely NO visual to represent a single value like a product price without any aggregation. It feels like I am missing a crucial part here or is that requirement sooo exotic?
Edit: Now I found the solution. So for anyone who is interested: the problem was that the category I mentioned above was also present in another table. I connected both in the data table and took the slicer with data from that other table. Now I have changed to the original pricing table and voilà it works!
"However, when I draw the avg Cat A onto a card it summarizes it" - a card requires an aggregation.
Are you getting the wrong number in the card or is it that the label text is confusing because it shows the aggregation?
Check out the November 2023 Power BI update to learn about new features.
Read the latest Fabric Community announcements, including updates on Power BI, Synapse, Data Factory and Data Activator.