The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
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.
Solved! Go to Solution.
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
Proud to be a Super User!
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
Proud to be a Super User!
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
User | Count |
---|---|
119 | |
86 | |
75 | |
55 | |
44 |
User | Count |
---|---|
136 | |
128 | |
78 | |
64 | |
63 |