Forum Discussion
Using Import mode for power bi dataset in Analysis Services
I am connecting to power bi dataset using connection string available in the power bi dataset settings using Analysis services import mode. but im not able to import the entire data. my dataset in power bi service has around 5 Mn rows, but the imported data only has approximately 3.5 Mn rows. Is there any limit on the number of rows i can import via Analysis services from a power bi dataset.
Hi Anonymous , Thank you for reaching out to the Microsoft Community Forum.
There is no hidden row limit when importing a Power BI dataset over the XMLA/Analysis Services endpoint, the engine returns whatever the semantic model currently contains. The behaviour you observed (3.5M -> 5M after adding an index) is consistent with a calculated table or partition that was not processed/rebuilt; your edit forced the model to re-evaluate and repopulate the table, which restored the full 5M rows.
Connect to the same dataset with SSMS, DAX Studio or Tabular Editor and run the partitions DMV (SELECT [Name],[RowCount] FROM $SYSTEM.TMSCHEMA_PARTITIONS;) and a DAX row count (EVALUATE { COUNTROWS('YourTableName') }) to confirm what the model currently stores. If the model shows ~3.5M, run a Process/Table or Process/Partition (or TMSL Refresh/ProcessFull) against that calculated table or its partitions to force a full rebuild. If it shows ~5M but Desktop imports 3.5M, ensure your import is pointed at the exact Initial Catalog (dataset/version) and that your identity has full visibility. To prevent recurrence, schedule explicit processing after any source update or avoid relying on implicit query edits to trigger model processing for calculated tables.
DAX Queries - DAX | Microsoft Learn
Process Database, Table, or Partition (Analysis Services) | Microsoft Learn
Partitions in Analysis Services tabular models | Microsoft Learn
11 Replies
- GeraldGEmerick
Memorable Member
Anonymous I am not aware of any limitation like that. You might want to try this technique: How to migrate Power BI datasets to Microsoft Analysis Services models [Tutorial]
- Nabha-Ahmed
Super User
Hi Anonymous
There is no row-limit when importing data from a Power BI dataset through the XMLA endpoint.
If you’re getting fewer rows (3.5M instead of 5M), this usually happens due to one of these reasons:RLS is applied → you only see rows allowed for your role.
Incremental Refresh is enabled → only active partitions are loaded.
Filters or query steps exist in the semantic model.
So the issue isn’t a limitation , it’s caused by a filter, RLS, or incremental refresh in the dataset. After removing or adjusting these, the imported row count will match the original dataset.I hope this help you !
- Nabha-Ahmed
Thanks for confirming.
In that case, there are two additional things you can check, as they often cause missing rows when connecting through XMLA:1. Partition row count mismatch inside the dataset
Even if Incremental Refresh is off, sometimes the model ends up with multiple internal partitions.
You can verify this by running:SELECT [Name], [RowCount]
FROM $SYSTEM.TMSCHEMA_PARTITIONSThis will tell us exactly how many rows the service has per partition and whether the total actually matches 5M inside the model.
---2. Relationship or filter propagation issue
If your table is fact-like, a relationship with a dimension table (with Cross filter direction = single) might reduce visible rows.
This won’t show as a Power Query filter but will still reduce the rows returned.You can test this by connecting to the dataset and running:
EVALUATE ROWCOUNT(FactTableName)
(Replace the table name.)
v-hashadapuCommunity Support
Hi Anonymous , Thank you for reaching out to the Microsoft Community Forum.
There is no hidden row limit when importing a Power BI dataset over the XMLA/Analysis Services endpoint, the engine returns whatever the semantic model currently contains. The behaviour you observed (3.5M -> 5M after adding an index) is consistent with a calculated table or partition that was not processed/rebuilt; your edit forced the model to re-evaluate and repopulate the table, which restored the full 5M rows.
Connect to the same dataset with SSMS, DAX Studio or Tabular Editor and run the partitions DMV (SELECT [Name],[RowCount] FROM $SYSTEM.TMSCHEMA_PARTITIONS;) and a DAX row count (EVALUATE { COUNTROWS('YourTableName') }) to confirm what the model currently stores. If the model shows ~3.5M, run a Process/Table or Process/Partition (or TMSL Refresh/ProcessFull) against that calculated table or its partitions to force a full rebuild. If it shows ~5M but Desktop imports 3.5M, ensure your import is pointed at the exact Initial Catalog (dataset/version) and that your identity has full visibility. To prevent recurrence, schedule explicit processing after any source update or avoid relying on implicit query edits to trigger model processing for calculated tables.
DAX Queries - DAX | Microsoft Learn
Process Database, Table, or Partition (Analysis Services) | Microsoft Learn
Partitions in Analysis Services tabular models | Microsoft Learn
- v-hashadapu
Hi Anonymous , hope you are doing great. May we know if your issue is solved or if you are still experiencing difficulties. Please share the details as it will help the community, especially others with similar issues.
- v-hashadapu
Hi Anonymous , Hope you are doing well. Kindly let us know if the issue has been resolved or if further assistance is needed. Your input could be helpful to others in the community.
