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

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Reply
JKlein
New Member

Dataverse Modeling

Hi,

 

I am trying to create a basic data model based on the 'Opportunity' and 'Goal' entities from Dataverse. However, I am wondering what the best approach and best practices are for creating relationships in Power Bi from Dataverse. Each relational table has natural IDs that can be used for connections (e.g., 'Client' with 'Opportunity' using AccountID/OpportunityID), but the question is, should they be used, or should I create separate index keys?

 

I would really appreciate your help.

1 ACCEPTED SOLUTION
VijayP
Super User
Super User

@JKlein 

 

You can just use the keys available in Dataverse and no need to create additional columns native power bi.

Actually that will cause more burden to Power BI Engine




Did I answer your question? Mark my post as a solution! Appreciate your Kudos!!
MY Blog || My YouTube Channel || Connect with me on Linkedin || My Latest Data Story - Ageing Analysis

Proud to be a Super User!


View solution in original post

1 REPLY 1
VijayP
Super User
Super User

@JKlein 

 

You can just use the keys available in Dataverse and no need to create additional columns native power bi.

Actually that will cause more burden to Power BI Engine




Did I answer your question? Mark my post as a solution! Appreciate your Kudos!!
MY Blog || My YouTube Channel || Connect with me on Linkedin || My Latest Data Story - Ageing Analysis

Proud to be a Super User!


Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

December 2024

A Year in Review - December 2024

Find out what content was popular in the Fabric community during 2024.