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

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
Poojara_D12
Super User
Super User

URGENT Help needed for Data Modeling

Spoiler
Hello community members:
I have a scenario where I'm facing an issue in the data that needs to be corrected and that needs help on the data modeling side.

Here's an insight on it:
The visual right now with applying the required filters: The highlighted one is the name, but the name is updated in the backend side but that doesn't reflects here in the visual.

Poojara_D12_0-1751277863398.png

 

When I convert it in a table visual and add the required field, here's the result:

Poojara_D12_1-1751278036464.png

 

it shows 3 names; the yellow one is highlighted is the name that is expected in the chart, but it shows the other one highlighted,

I think there's something with the data modeling (one-to-many relationship), which I'm not able to figure out.

 

Can anyone please help? It will really be helpful to me. 

Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos"

Kind Regards,
Poojara - Proud to be a Super User
Data Analyst | MSBI Developer | Power BI Consultant
Consider Subscribing my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS
2 ACCEPTED SOLUTIONS
DataVitalizer
Solution Sage
Solution Sage

Hi @Poojara_D12 


Make sure the relationship is active, one-to-many, and the key column on the "one" side is unique.

Did it work 👍 A kudos would be appreciated ‌‌📢 Mark it as a solution to help spreading knowledge

View solution in original post

v-hashadapu
Community Support
Community Support

Hi @Poojara_D12 , Thank you for reaching out to the Microsoft Community Forum.

 

Your data model likely includes both old and new name entries and the visual is pulling from the wrong source, probably the fact table or a merged dataset. Even with a correct relationship, if the dimension table isn’t cleaned to keep only the latest name per ID, the outdated one can still show up.

 

To fix it, ensure your visual uses the name from a cleaned dimension table where each ID maps to a single, up-to-date name. In Power Query, filter the dimension to keep only the latest name per ID (e.g., using Group By with a max date). Then verify the relationship is active and based on ID. This will ensure your visual reflects only the current name.

 

If this helped solve the issue, please consider marking it “Accept as Solution” so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.

View solution in original post

3 REPLIES 3
v-hashadapu
Community Support
Community Support

Hi @Poojara_D12 , hope you are doing great. May we know if your issue is solved or if you are still experiencing difficulties. Please share the details as it will help the community, especially others with similar issues.

v-hashadapu
Community Support
Community Support

Hi @Poojara_D12 , Thank you for reaching out to the Microsoft Community Forum.

 

Your data model likely includes both old and new name entries and the visual is pulling from the wrong source, probably the fact table or a merged dataset. Even with a correct relationship, if the dimension table isn’t cleaned to keep only the latest name per ID, the outdated one can still show up.

 

To fix it, ensure your visual uses the name from a cleaned dimension table where each ID maps to a single, up-to-date name. In Power Query, filter the dimension to keep only the latest name per ID (e.g., using Group By with a max date). Then verify the relationship is active and based on ID. This will ensure your visual reflects only the current name.

 

If this helped solve the issue, please consider marking it “Accept as Solution” so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.

DataVitalizer
Solution Sage
Solution Sage

Hi @Poojara_D12 


Make sure the relationship is active, one-to-many, and the key column on the "one" side is unique.

Did it work 👍 A kudos would be appreciated ‌‌📢 Mark it as a solution to help spreading knowledge

Helpful resources

Announcements
November Power BI Update Carousel

Power BI Monthly Update - November 2025

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

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!

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