Forum Discussion
Using Import mode for power bi dataset in Analysis Services
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
Just an update: if i make any change in the source query which is used in my calculated table (of Source dataset), im getting the correct count loaded : eg: I added an index column in the source query , now the full data is getting loaded.
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