Forum Discussion
Power BI Service – Card Visual Values Conflict Post Refresh
Power BI Service – Card Visual Values Conflict Post Refresh
I’ve developed a Sales Analysis report in Power BI with key metrics shown through card visuals such as:
-
Total Sales: 6,500
-
Total Quantity: 500
These values are accurate and consistent in Power BI Desktop.
However, after publishing to Power BI Service and configuring Row-Level Security (RLS) and Scheduled Refresh, I’ve noticed a strange issue:
After 2–3 refreshes, card visuals sometimes show unexpected doubled values, like:
-
Total Sales: 13,000
-
Total Quantity: 1000
Interestingly, these values seem to correct themselves automatically after some time or when the visuals refresh again.
During investigation, I found:
-
No duplication in Power Query.
-
But duplicates appear in the table view in Power BI Desktop after refreshes in Service.
-
Eventually, the visuals revert back to correct values (6,500 / 500), but this inconsistency has occurred multiple times.
I’m looking to understand:
-
What could cause temporary data duplication or inflated values post-refresh?
-
Could RLS or Service refresh behavior be involved?
-
How to ensure consistent visual results between Desktop and Service?
Any insights or suggestions would be greatly appreciated!
Hi Anonymous
Yes the issue is solved just two days back, the issue was from the API side and Microsoft Support ticket is been closed from our end. We have changed the source(to sql) and the issue is solved now.
Thank you so much for the help!
8 Replies
Hi Poojara_D12 ,
We’re following up once more regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?
If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.
Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.
Thank you for your understanding and participat
Hi Anonymous
Yes the issue is solved just two days back, the issue was from the API side and Microsoft Support ticket is been closed from our end. We have changed the source(to sql) and the issue is solved now.
Thank you so much for the help!
My money is on timezone mismatch.
Timezone is same, for client and me.
Hi Poojara_D12 ,
Thanks for reaching out to the Microsoft Fabric Community.
The issue you're encountering where card visuals temporarily show inflated values after a scheduled refresh appears to be due to transient caching behavior in Power BI Service or Row-Level Security (RLS) misconfiguration.
Try this troubleshooting steps which help’s resolving your issue:
- Review your RLS filters under Modeling > Manage Roles and ensure filters are correctly scoped to the fact table. Test using "View As Role".
- Check Power Query for duplicates especially in Merge or Append steps. Apply Remove Duplicates using unique keys like Invoice or Transaction ID.
- Disable Auto Page Refresh, if enabled, to prevent visuals from rendering prematurely during model refresh.
- Monitor refresh history logs in the Power BI Service to check for overlapping or failed refreshes.
These steps should eliminate the temporary inconsistencies and ensure stable, accurate visuals across both Desktop and Service.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thankyou.
Hi Poojara_D12 ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.Hi Anonymous lbendlin
Thank you very much for your feedback. However, the issue remains unresolved.
We have already created a support ticket with Microsoft and have had 3–4 meetings with their support team. Despite these efforts, the issue/bug still persists.
