Report with Live Connection and RLS Not Reflecting Correct Data for Some Users

[ddd11]

Description:

We have a Power BI report published in Workspace A that uses a live connection to a dataset in another workspace called "Master Database". This dataset has Row-Level Security (RLS) implemented.

A client (with proper RLS role assignment) is experiencing an issue where they cannot see all the campaign data they should have access to when using the original report link.

As a test, we downloaded the same report (which uses the live connection), renamed it, and republished it to the same workspace. Surprisingly, the user is now able to see all their accessible campaigns correctly in the new report.

We suspect the issue lies with RLS metadata caching or connection state in the original report.

What we've confirmed:

• The client has the correct RLS role in the dataset.

• The dataset itself is functioning correctly.

• Only the original report (original link) seems to show incorrect or partial data.

• Republishing a copy of the report resolves the issue, but this creates a new link and report ID, which we want to avoid.

Request:

Is there a way to force the original report to re-evaluate RLS rules or refresh its metadata without needing to create a new report (i.e., keep the same link)?

Any insights or best practices to avoid this issue in the future would also be appreciated.

Thanks!

[v-sathmakuri]

Hi @ddd11 ,

I hope the information provided is helpful. Feel free to reach out if you have any further questions or would like to discuss this in more detail. If responses provided answers your question, please accept it as a solution so other community members with similar problems can find a solution faster.

Thank you!!

[v-sathmakuri]

Hi @ddd11,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you!!

[v-sathmakuri · Accepted solution]

Hi @ddd11 ,

Thank you for reaching out to Microsoft Fabric Community.

You can try using the Rebind Report API, which allows you to rebind the existing report without changing its report ID or link to the same dataset. This action forces Power BI to refresh the report’s internal metadata, including Row-Level Security (RLS) role evaluations and identity bindings.
For more details, refer to the official documentation: https://learn.microsoft.com/en-us/rest/api/power-bi/reports/rebind-report )

sample call:

POST https://api.powerbi.com/v1.0/myorg/groups/{groupId}/reports/{reportId}/Rebind
Content-Type: application/json

{
"datasetId": "your-dataset-id"
}

Additionally, although reports with live connections don't typically require dataset refreshes, you may try triggering a dataset refresh from the source workspace. In some cases, this can help clear cached role assignments or identity tokens that may be impacting RLS behavior.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thank you!!

[ddd11]

Dear @Deku ,
Thank you for your reply.

I have tried this with no success, I believe it's related to power BI service Cash on RLS Side when it's connected live.

[Deku]

Could have the user clear their browser cache or log off and back in again, see if that has any affect

[ddd11]

Hello @Deku ,
I have republished the report with a new link. But, still I have fear that this problem happened again.
I want to know how can we solve this issue once for all.

[v-sathmakuri]

Hi  @ddd11 , 

Thank you for reaching out to Microsoft Fabric Community.

Have the user log out of Power BI and log back in. This can refresh their session and force Power BI to reapply the correct RLS roles when they access the report again.

Clear the cache in the user’s browser or have them access the report in InPrivate or Incognito mode.

If the above does not resolve the issue, since your report uses a live connection to the dataset, RLS is evaluated at query time. To avoid issues, try changing it to Import Mode and schedule the refresh as per your requirements.

 

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thank you!!

[v-sathmakuri]

Hi @ddd11 ,

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 the responses has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you!!