Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
I have 2 Power BI Reports , data source for both reports are different.
I have imported Semantic Model of Primary report in Secondary report-PB Desktop and created relationship between Primary and Secondary with SKU No. as common.
But when I created table in visuals to compare Primary to Secondary, the YTD sales of Secondary is showing wrong nos. while YTD Primary is showing correct no.
Can anyone tell why Secondary nos. are coming wrong? What relationship i can created to make this right?
Solved! Go to Solution.
Hi @AartiD - If you can’t merge Date tables, you can try userrelationship() in your secondary YTD
Eg:
YTD Secondary Sales =
CALCULATE(
TOTALYTD(SUM(Secondary[SalesAmount]), Secondary[OrderDate]),
USERELATIONSHIP(Secondary[SKU], Primary[SKU])
)
But this is less ideal because YTD always needs a date context, not SKU context.
Check and confirm.
Proud to be a Super User! | |
Hi AartiD,
We wanted to see if the information we gave helped fix your problem. If you need more help, please feel free to contact the Microsoft Fabric community.
Thank you.
Hi AartiD,
We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.
Thank you.
Hi AartiD,
We would like to follow up and see whether the details we shared have resolved your problem.
If you need any more assistance, please feel free to connect with the Microsoft Fabric community.
Thank you.
Thankyou, @rajendraongole1, for your response.
Hi AartiD,
We appreciate your inquiry via the Microsoft Fabric Community Forum.
Based on my understanding, the secondary YTD figures are incorrect because the secondary fact table is directly joined to the primary fact table using the SKU. Time-intelligence functions such as TOTALYTD and DATESYTD operate correctly only when each fact table is connected to a properly marked Date table. Fact-to-fact joins prevent correct filter propagation.
Please follow the steps below to help resolve the issue:
We hope the information above helps to resolve the issue. If you have any further queries, please feel free to contact the Microsoft Fabric Community.
Thank you.
Hi @AartiD - If you can’t merge Date tables, you can try userrelationship() in your secondary YTD
Eg:
YTD Secondary Sales =
CALCULATE(
TOTALYTD(SUM(Secondary[SalesAmount]), Secondary[OrderDate]),
USERELATIONSHIP(Secondary[SKU], Primary[SKU])
)
But this is less ideal because YTD always needs a date context, not SKU context.
Check and confirm.
Proud to be a Super User! | |
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
Check out the October 2025 Power BI update to learn about new features.