Forum Discussion
Get Partition # rows for Incremental Refresh
Hi guys,
I'm trying to see my partitions row count for a Power BI Premium dataset that is using incremental refresh. However they all show up as 0.
I'm connecting to the dataset using SSMS and it does show all the partition names, but for #rows, they're all 0. I know they have data because the report is working and updating as expected. There are millions of rows of data in the dataset.
I'm hoping this is an easy fix where I just need to enable something. Any ideas?
Thanks
Hi BizIntel ,
Did you connect to the dataset using the steps in the document below?
Dataset connectivity and management with the XMLA endpoint in Power BI
Best Regards,
Community Support Team_GaoIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly. If I misunderstand your needs or you still have problems with it, please feel free to let us know. Thanks a lot!
How to get your questions answered quickly -- How to provide sample data
3 Replies
Hi BizIntel ,
Did you connect to the dataset using the steps in the document below?
Dataset connectivity and management with the XMLA endpoint in Power BI
Best Regards,
Community Support Team_GaoIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly. If I misunderstand your needs or you still have problems with it, please feel free to let us know. Thanks a lot!
How to get your questions answered quickly -- How to provide sample data
Hi Team Gao,
I thought I was following those directions. But apparently there is 1 crucial caveat -
- In order to see the number of rows in a dataset partition, you have to specify the dataset in the initial catalog in the connection options
- However, for every dataset in the workspace, you can still see the partitions and even when they were last updated, just not the number of rows
Thank you for pointing me in the right direction.
in order to see the partitions of a dataset, you
I faced the same issue. To me it sounds like a bug and MS should fix it.
