Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and a 50 percent discount on exams.
Get startedEarn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
Hi Guys,
We have below calculation group code for single fact which works fine, we are calling other measure which we create tocalaulate amount along with cal item
Solved! Go to Solution.
Hi @navind ,
It seems like you're trying to apply a calculation item across different fact tables, but you're encountering issues with skewed numbers.
Firstly, it's important to ensure that your calculation item logic correctly identifies the relevant Product IDs across all fact tables. The approach you've taken with the CONTAINS function should work in theory, but it's crucial to ensure that the relationships between your fact tables and the dimension table containing the Product IDs are correctly set up in your model. This ensures that the CONTAINS function can accurately filter the rows.
However, using CONTAINS in this manner might not be the most efficient way to filter for "Grade1" across multiple fact tables. Instead, consider leveraging the existing relationships in your model. If your fact tables are related to a common dimension table (e.g., a Product dimension table), you can simplify your calculation item by filtering on this dimension table directly, assuming that the ProductID "Grade1" is present in this dimension.
Here's a revised approach:
Calculation item =
CALCULATE(
SELECTEDMEASURE(),
FILTER(
ALL('ProductDimension'),
'ProductDimension'[ProductID] = "Grade1"
)
)
In this revised approach, replace 'ProductDimension' with the actual name of your Product dimension table that is related to your fact tables. This method assumes that there's a single, consistent Product dimension that all your fact tables relate to, which simplifies the filtering logic.
Best regards,
Community Support Team_Binbin Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @navind ,
It seems like you're trying to apply a calculation item across different fact tables, but you're encountering issues with skewed numbers.
Firstly, it's important to ensure that your calculation item logic correctly identifies the relevant Product IDs across all fact tables. The approach you've taken with the CONTAINS function should work in theory, but it's crucial to ensure that the relationships between your fact tables and the dimension table containing the Product IDs are correctly set up in your model. This ensures that the CONTAINS function can accurately filter the rows.
However, using CONTAINS in this manner might not be the most efficient way to filter for "Grade1" across multiple fact tables. Instead, consider leveraging the existing relationships in your model. If your fact tables are related to a common dimension table (e.g., a Product dimension table), you can simplify your calculation item by filtering on this dimension table directly, assuming that the ProductID "Grade1" is present in this dimension.
Here's a revised approach:
Calculation item =
CALCULATE(
SELECTEDMEASURE(),
FILTER(
ALL('ProductDimension'),
'ProductDimension'[ProductID] = "Grade1"
)
)
In this revised approach, replace 'ProductDimension' with the actual name of your Product dimension table that is related to your fact tables. This method assumes that there's a single, consistent Product dimension that all your fact tables relate to, which simplifies the filtering logic.
Best regards,
Community Support Team_Binbin Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
User | Count |
---|---|
93 | |
86 | |
78 | |
72 | |
66 |
User | Count |
---|---|
115 | |
106 | |
85 | |
65 | |
64 |