Share via

CountRows Function Miscalculating PowerBi

Anonymous
2025-03-28T21:24:19+00:00

I have 1295 rows in my Power Bi table.

I uploaded new rows to my data source and did a refresh in Powerbi, but the CountRows calculation is still showing my previous number of rows at 1185. I deleted the measure and typed a new measure but it is still showing 1185.

I then added a new column and used the function count = 1. It is still pulling a total of 1185.

What could be the cause?

Resolved: I had to delete my data source and re-upload. Then fix all my values in my visuals.

Microsoft 365 and Office | Install, redeem, activate | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-03-29T00:52:36+00:00

    Dear respected,

    Thank you for posting in Microsoft Community. We truly appreciate the time you've taken to troubleshoot thee issue and share the resolutions back here. It's good to hear that you managed to resolve the issue by delete the data source and re-upload. This is indeed a good refresh way to troubleshoot this kind of scenario.

    To help other community members who might encounter a similar issue, I made a summary of your caseand so others can easily find the possible resolution based on their environment.

    Issue description

    =============

    There is a problem with the CountRows function in Power BI. Despite having 1295 rows in the Power BI table, the CountRows calculation continued to show the previous number of rows, which was 1185. 

    Issue Environment:

    =============

    • Power BI
    • Data source with 1000+ rows

    Troubleshooting ways

    =============

    Deleting and re-typing the measure (persisted)

    Adding a new column with the function count = 1 (persisted)

    Solution:

    =============

    The user resolved the issue by deleting the data source and re-uploading it. After re-uploading, it fixed all the values in the visuals, which corrected the CountRows calculation to reflect the accurate number of rows.

    If you find this summary helpful, feel free to use the feedback tool under this reply to give feedback. This will assist other community members with similar questions can easily find your threadfor their reference andtry the same solution that worked on your side more efficiently.

    Image

    Feel free to post new threads in this community whenever you encountered other scenarios. We're always here to assist you.

    Thank you for your cooperation. We hope you have a wonderful day and stay safe and healthy! 😊

    Sincerely,

    Mia | Microsoft Community Moderator

    Was this answer helpful?

    0 comments