Now Available in Community - New TechTalk Videos for 2020
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Which would be considered the best approach in creating a Data Entity and using them in Power BI.
1. Create Data Entity by joining various tables and then fetch them in Power BI
2. Create separate entities for different tables and then fetch them in Power BI and relate them accordingly.
It will be better to create a single entity. It will simplify the process. Maybe a bit more development needed.
Also, a single entity will probably result in a higher response rate than multiple ones.
Sometimes it becomes very complex to present multiple tables as a single entity - look at CustCustomerV3Entity. But that is mostly because of inserts and updates. With powerBi you are only reading, thus it shouldn't be a problem.
I can see both options in use
if relations are straightforward then building them in data entity is preferred
if relations and conditions are complex then consider joining in PowerBI
We use second approach. Create standalone entities for the tables which are needed , publish them to BYODB and write direct queries to fetch data in power BI reports.
I have limited knowledge of PowerBI, so if I were you, I'd take Sukrut's advice.
Business Applications communities