The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
My situation is something like the following:
Clothing seller wants to know what combination of shirts are sold together. One table (SALES) exists to track all sales. I want to be able to select 2 shirts from the same or different slicers (whichever method works) and see the count of sales and possibly other fields from SALES. We will know they are from the same order when they have the same date and time (ORDERDATE) + customer (CUSTOMER) + cashier (CASHIER).
Getting it to work with exactly 2 selections would be fantastic and completely acceptable. Allowing for an unknown number (n>1) of selections would be the perfect solution.
Does anyone have an idea of how to approach this problem?
Solved! Go to Solution.
@pschommer,
Create a orderid column in SALES table using the DAX below.
orderid = CONCATENATE(SALES[CASHIER],CONCATENATE(SALES[CUSTOMER],SALES[ORDERDATE]))
Then create the OrderID table with the following DAX.
After that, create a relationship between SALES table and the new OrderID table using the ordered column, and you will get expected result by creating three custom columns(Red, Blue and White) following smoupre's suggestion.
OrderID Table = DISTINCT(SALES[orderid])
Regards,
Lydia
Can you provide sample data? The structure of your Sales table is going to determine how best to achieve this.
I kept it simple. Something like THIS.
If I'm looking at it correctly...
Bonus points for...
Not sure about slicers, but you could do it with filters.
Basically, create an OrderID table that has a unique key for your order ids. Create a related custom column in your sales table. I just concatenated your three values together.
Relate the tables. In your OrderID table create these columns:
Red = CALCULATE(SUM(Sales[Quantity]),FILTER(RELATEDTABLE(Sales),[ItemDesc] = "Red Shirt")) Blue = CALCULATE(SUM(Sales[Quantity]),FILTER(RELATEDTABLE(Sales),[ItemDesc] = "Blue Shirt")) White = CALCULATE(SUM(Sales[Quantity]),FILTER(RELATEDTABLE(Sales),[ItemDesc] = "White Shirt"))
Create a table visualization based on the OrderID table and put OrderID in it. Add a filter for Red is not Blank and Blue is not Blank. You will get your four orders. Add a filter for White is not blank. You get your two orders, etc.
Thank you for your reponse. A quick clarification, if I may.
On the SALES table, I can create the concatenated OrderID field.
On the new OrderID table, how do you create unique key values (that I think you want to match with the concatenated values from SALES) when you don't know what those values are? New values are being created all the time and you won't know part of OrderID (Customer name).
I think I understand the rest of your suggestion. Does my question make sense?
@pschommer,
Create a orderid column in SALES table using the DAX below.
orderid = CONCATENATE(SALES[CASHIER],CONCATENATE(SALES[CUSTOMER],SALES[ORDERDATE]))
Then create the OrderID table with the following DAX.
After that, create a relationship between SALES table and the new OrderID table using the ordered column, and you will get expected result by creating three custom columns(Red, Blue and White) following smoupre's suggestion.
OrderID Table = DISTINCT(SALES[orderid])
Regards,
Lydia
Thank you to @v-yuezhe-msft and @Greg_Deckler for walking me through this.
The New Table definition based on a function that points to a different table is the unexpected learning for me in this exercise. Although I definitely needed every bit of advice to make it all work. Now that I have this simple example working properly, I will see if I can get it to work with my real dataset.
Your efforts are appreciated!
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
User | Count |
---|---|
109 | |
76 | |
65 | |
52 | |
51 |
User | Count |
---|---|
128 | |
117 | |
78 | |
65 | |
63 |