Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Hi All, something very strange is happening.
I've just created a new Power BI file with data from Dataverse.
I'm pulling all accounts from our environment.
I'm using my system admin account.
In Dynamics CRM, I can see 4225 active accounts, but in Power BI, only 815 rows. There are no filters or applied steps to the account table pulled from Dataverse
Here is my Advanced Query:
let
Source = CommonDataService.Database("myorg.crm4.dynamics.com"),
dbo_account = Source{[Schema="dbo",Item="account"]}[Data],
#"Removed Other Columns" = Table.SelectColumns(dbo_account,{"accountid", "name", "accountnumber", "owneridname", "syn_account_typename", "syn_address1_country_idname", "syn_customer_group_idname", "syn_key_accounter_idname", "syn_key_accounter_idyominame", "syn_industryname", "syn_internal_salesname", "syn_account_sales_managername", "syn_sales_divisionname", "syn_company(accountid)"})
in
#"Removed Other Columns"
Any idea what to check to see also 4225 rows in PBI?
Regards,
Kiril
Solved! Go to Solution.
The solution was simpler! I just cleared all permissions from the datasource settings. Apparently something was cached, so I started fresh, and now I can see everything properly
The solution was simpler! I just cleared all permissions from the datasource settings. Apparently something was cached, so I started fresh, and now I can see everything properly
So, there are three connectors: Dynamics CRM Online (legacy), Dynamics CRM (Dataverse), and Dataverse only (part of Power Platform). neither returned the amount of records I was expecting.
Regardnless of the connector used the Query is always refeering to
let
Source = CommonDataService.Database("vossfluid.crm4.dynamics.com"),
dbo_account = Source{[Schema="dbo",Item="account"]}[Data]
in
dbo_account
This happend recently because if a load some of the previous reports developed by myself before refreshing the data i can see around 3000 Accounts, after i refresh the report its updated to 400.
I've tested both Import and Direct Query and both shows the same 815 Accounts instead of 4225
Neither of these actions worked. I even created a new report using the Dataverse connector, connected only to the Accounts table, and still 815 record. My System user's account, as I show on the picture, can be seen 4225 Account in CRM, and netiher one of them are owned by me as I don't own records as a system admin. After loading the dataverse connector the advanced editor query still shows: let
Source = CommonDataService.Database("myorg.crm4.dynamics.com"),
dbo_account = Source{[Schema="dbo",Item="account"]}[Data]
And if try to use the query provided here:
let
Source = Dataverse.Database("myorg.crm4.dynamics.com"),
Account = Source{[Name="accounts"]}[Data]
in
Account
It gives me the following error message:
The import Dataverse.Database matches no exports. Did you miss a module reference?
Hi @radoslavov91 ,
Thank you for reaching out to Microsoft Fabric Community.
This is a common issue when working with Dataverse in Power BI. Even though you're using a System Admin account, there are a few things that can limit the number of rows you see:
The reason Why you're only seeing 815 rows:
Old Connector - You're using the Common Data Service (Legacy) connector. This often applies hidden filters or permissions.
Security Roles - Power BI still respects Dataverse security roles. Even admins can be limited by things like business units or ownership of records.
Auto-applied Filters - Sometimes, Power BI applies hidden filters from relationships or related tables (like lookups or navigation columns).
You can do following steps to fix it:
1.Use the new Dataverse connector
Replace your current query with this:
let
Source = Dataverse.Database("myorg.crm4.dynamics.com"),
Account = Source{[Name="accounts"]}[Data]
in
Account
2.Check for hidden filters
In Power Query, look at the "Applied Steps" and make sure nothing is reducing your rows.
3.Check security in Dataverse
Even if you're an admin, confirm your account can access all records, not just the ones you own.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thank you.
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
| User | Count |
|---|---|
| 97 | |
| 71 | |
| 50 | |
| 46 | |
| 44 |