Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I am a Power BI report developer connecting to the Dynamics CRM via Power Query using Import Mode. I have a choice of the Dataverse Connector ( CommonDataService.Database ) or SQL Server ( Sql.Database with port number 5558 )
I prefer the SQL Server connector as I can write my own SQL Query against it. The tables seem to be the same. Are there any issues using SQL Server connector over the Dataverse Connector?
The only problem which I can think of is Lookup name and optionset text value. You can still get these values by joining your table with string map and with related entity when you use direct SQL query. However you can easily get these values as part of the same table when you use Dataverse connector.
Other than this I don't think there should be any issue.
You can also find great article below which compares different ways to connect to Dataverse from Power BI.
Please mark my answer verified if this is helpful!
Follow my Blog: xrmdynamicscrm.wordpress.com/
Business Applications communities