Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hello, I am experiencing an unexpected issue with a calculated column and I am wondering if it has to do with the way I created the table it is referencing. I have the following tables:
1. Unfiltered Forecast - Created using SUMMARIZE with master data import tables
2. Unfiltered Demand - Created by grouping by inventory ID # and contains a calculated column which references the Unfiltered Forecast table
3. Filtered Forecast - Created using a UNION on two tables
4. Filtered Demand - Created by grouping by inventory ID # and contains a calculated column which references the Filtered Forecast table
Here is the calculated column used in #2:
Solved! Go to Solution.
Thanks for the response, @AllisonKennedy. I ended up adding additional context to the original formula which allowed the calculation to execute at the row-level. The end result needed to be a summation of quantities for each item in a given time period based on a transaction table with many transactions for that item. I have it working now, I also took your advice on the DimDate table, thanks for the tip.
@cpiercey
I wonder why do you create the column in table 4 while it calculate with the column in table 3. Why don't you just create the column in Table 3.
Basically the expression column of Calculate(xxxx) must from the current table, you can filter with others tables if there is a relationship, something like:
2018 Q1 Demand = CALCULATE(sum('Filtered Demand'[Total Quantity]), 'Filtered Forecast'[Date - Year] = 2018, 'Filtered Forecast'[Date - Quarter] = 1)
Paul Zheng _ Community Support Team
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Copying DAX from this post? Click here for a hack to quickly replace it with your own table names
Has this post solved your problem? Please Accept as Solution so that others can find it quickly and to let the community know your problem has been solved.
If you found this post helpful, please give Kudos C
I work as a Microsoft trainer and consultant, specialising in Power BI and Power Query.
www.excelwithallison.com
Thanks for the response, @AllisonKennedy. I ended up adding additional context to the original formula which allowed the calculation to execute at the row-level. The end result needed to be a summation of quantities for each item in a given time period based on a transaction table with many transactions for that item. I have it working now, I also took your advice on the DimDate table, thanks for the tip.
Copying DAX from this post? Click here for a hack to quickly replace it with your own table names
Has this post solved your problem? Please Accept as Solution so that others can find it quickly and to let the community know your problem has been solved.
If you found this post helpful, please give Kudos C
I work as a Microsoft trainer and consultant, specialising in Power BI and Power Query.
www.excelwithallison.com
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
113 | |
99 | |
80 | |
70 | |
59 |
User | Count |
---|---|
149 | |
114 | |
107 | |
89 | |
67 |