Help with DAX Formula.!

[Vamshi_PBI]

Hi Team,

I need some help with writing dax formula. PFB details.

My data model is having 3 tables and the data modelling as below . So i would like to take product key, product foreign key into table visual and dispaly the total sum of amount (150) againist each row by using ALL function as below.

All Amount = CALCULATE(SUM(FactSales[Amount]),ALLSELECTED(FactSales))

But as soon as I include ALL or ALLSelected a Cross Join is happening between productkey and productforeign key.

In the same way, I would need total PurchaseAmount also into the same table visual and i'm writing formula as below.

PurchaseAmount_ALL = CALCULATE(CALCULATE(SUM(Purchases[PurchaseAmount]), CROSSFILTER(FactSales[PurchaseForeignKey],Purchases[PurchaseKey],Both),CROSSFILTER(DIMProduct[Productkey],FactSales[ProductForeignKey],Both)),ALLSELECTED(FactSales))

So basically, I want to do PurchaseAmount_ALL/All Amount, so that i can display the result againist each row. I attached a screenshot how the output should be. (2100/150 = 14 againist each row)

So, Two scenarios are same, i would like to alter context by using ALL or ALLSelected, but cross joining is happening.

Please help with this, any help is very much appreciated.

Thanks.

[Anonymous]

Hi @Vamshi_PBI ,

Please try to use columns.

How to Get Your Question Answered Quickly 

If it does not help, please provide more details with your desired output and pbix file without privacy information (or some sample data) .

Best Regards
Community Support Team _ Rongtie

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Vamshi_PBI]

Hi @Anonymous ,

Thank you for the support, This solution is working but when i select any of the productkey or foreign key only the sum of that should reflect but it is not right now. for example if i select product 1 and 2, then only 200 should reflect for all rows but it is showing 400 only, the filter is not working. Moreover we have combination of direct query and live model, so calculated columns would result performance issue.

Thanks.