SOLVED

Drag Dax measures into Y-axis of clustered bar chart for getting count of dates

Brass Contributor

Hi @Sergei Baklan ,

 

We have a table like this below:

Excellove15_0-1709204678374.png

Based on few conditions on Invoice/Credit column of this table, we need to count the Date column of this table and use this count for showing the users that this many counts fall under below:

 

Multiple Invoices

Credit cancels Invoices

Invoice-Credit Value Mismatch

Multiple Credits

 

expected outcome:

Excellove15_1-1709205162458.png

 

You helped us creating the conditions in the form of Dax measures instead of calculated columns as below:

Excellove15_2-1709205392887.pngExcellove15_3-1709205417518.png

Excellove15_4-1709205485457.png

Based on above conditions, we created a calculated column as below to create the status column but this still causes performance issues:

Excellove15_5-1709205629860.png

 

So we thought of breaking this into small measures each like below although not sure whether it is correct or not!

Excellove15_6-1709206204515.png

Excellove15_7-1709206285219.png

Excellove15_8-1709206329924.png

Excellove15_9-1709206359066.png

Now in visual, we are not able to drag these Dax measure on y-axis of the clustered bar chart as shown below:

Excellove15_10-1709206478124.png

 

If you have different ideas/different way to achieve the requirement, please let us know sir

PFA file here PR-419 - Data Coverage RLS ADB (2).pbix

 

Thanks in advance!

 

 

2 Replies
best response confirmed by Excellove15 (Brass Contributor)
Solution

@Excellove15 

Nope, I have no other ideas. We can't use measures both in X and Y axis's. As for the performance that's only to play with options. Perhaps another calculated table could work, not sure.

Hi @Sergei Baklan 

 

Thanks for your quick response Sir!:smile:

Nop! I will close this query now!

 

Thanks!

1 best response

Accepted Solutions
best response confirmed by Excellove15 (Brass Contributor)
Solution

@Excellove15 

Nope, I have no other ideas. We can't use measures both in X and Y axis's. As for the performance that's only to play with options. Perhaps another calculated table could work, not sure.

View solution in original post