Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Reply
AartiD
Helper II
Helper II

Semantic Model Importing in another PBI report

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?

1 ACCEPTED SOLUTION
rajendraongole1
Super User
Super User

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.





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!





View solution in original post

5 REPLIES 5
v-pnaroju-msft
Community Support
Community Support

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.

v-pnaroju-msft
Community Support
Community Support

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.


v-pnaroju-msft
Community Support
Community Support

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.

v-pnaroju-msft
Community Support
Community Support

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:

  1. Create a single Date table and mark it as a Date table.
  2. Relate the Date table to both the primary and secondary fact tables using one-to-many relationships with single directional filtering. Avoid fact-to-fact joins.
  3. Rebuild the Secondary YTD measure so that it references the Date table.

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.

rajendraongole1
Super User
Super User

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.





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!





Helpful resources

Announcements
Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

October Power BI Update Carousel

Power BI Monthly Update - October 2025

Check out the October 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors