Has something changed with the Power BI dataflows (Legacy) connector, recently?

Datasets which use this legacy connector to direct query dataflows are now failing - and need changed to the 'non-legacy' version.

#PowerBI #dataflows #legacy #DirectQuery

**Updated** 📊 #PowerBI templates for #Dynamics365
⭐These Power BI-based sales reports for D365 Sales and optional managed/unmanaged solutions are available to try out today.
⭐They have been updated with a new Salesperson report embedded directly in the user form.
⭐It also includes some minor formatting updates and a bugfix for the “closing percentage” measure.
⭐The github repository includes examples using Dataverse’s SQL TDS endpoint for both #import and #DirectQuery - along with examples using #SynapseAnalyticsLink for higher volume datasets.

📖Details on configuration and installation are on the ReadMe doc and you can
🔗download all templates and solution files from the repository from my GitHub repository: https://github.com/mscottsewell/Power-BI-D365-Sales

📺Here's a short video describing the solution installation: https://www.youtube.com/watch?v=mcdpm_5skpA

#powerbi #sales #dynamics365 #dynamicscrm #video

Really interesting performance results using #PowerBI #DirectQuery against #Dataverse today.
I found that DirectQuery against Dataverse can successfully fold the queries and refresh the report in a not-unreasonable amount of time, *even if the dataset for the tables would exceed the TDS endpoint's 80MB per query size limit.*
Backstory is that I'm working with a dataset of 421K Service Case records in Dynamics 365 CE and testing different ways to build the dataset in Power BI. I'm getting a page crammed full of 9 separate visuals refreshed in about 11 seconds. I was surprised by the reasonable performance since Direct Query is never my first choice for speed.
I thought for comparison, I'd try switching to import mode - and found it would immediately hit the current size limit and fail.
My take-away was that a well-structured set of queries can leverage Power BI Direct Query to pull metrics from tables that are too large to import. 👍
#powerbi #dataverse #powerplatform #dynamics365

📊⚡ Using #PowerBI over #Dataverse data? Whether you are a #Dynamics365 or #PowerApps customer, this MUST-READ content will help you create fast and efficient reports.

Considerations when connecting #PowerBI to #Dataverse
💡 Query performance
💡 Data volume
💡 Data latency
💡 Role-based security
💡 Setup complexity

Recommended best practices
⚡Focus on a specific use case
⚡Design a star schema
⚡Optimize Power Query queries
⚡Minimize the number of query columns
⚡Write native queries
⚡Execute native queries with the EnableFolding option
⚡Speed up the evaluation stage

Work with large datasets with #AzureSynapse Link
💫 Create an Azure Synapse Link for Dataverse
💫 Create a second serverless SQL pool
💫 Create custom views
💫 Query appropriate tables
💫 Connect to Synapse Analytics

Considerations for #DirectQuery
⏱️ Use dual storage mode dimension tables
⏱️ Enable single-sign on
⏱️ Replicate "My" filters in Power Query
⏱️ Create supplementary import models

https://aka.ms/D365PBI