Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
RLS sometimes disappears at publish, I looked up and it says it might be due to ownership change, but it also sometimes happens when I'm publishing and I'm the owner.
and sometimes ownership does change and it doesn't get removed
Any ideas?
Solved! Go to Solution.
Hi @M-IMS ,
The issue of RLS disappearing upon publishing in Power BI can occur due to various reasons, including dataset overwrites, workspace permissions, and inconsistencies in ownership changes. While a change in ownership is a known cause, it is not always consistent, which explains why RLS sometimes remains intact even after an ownership change. If you are the owner and still facing this issue, it could be due to republishing a dataset from Power BI Desktop, which might reset or remove RLS roles if the dataset structure has changed. Additionally, if multiple contributors have access to the workspace, someone else may have modified the dataset, leading to RLS inconsistencies.
Another possible reason is the use of different development environments or shared datasets, where rebinding or reconnecting a dataset in Power BI Service can sometimes reset RLS. To prevent this, ensure that RLS is properly defined before publishing, check if the dataset is being replaced, and reapply RLS settings in the Power BI Service if necessary. Using Deployment Pipelines or version control can help maintain consistency across environments. If the issue persists, testing with a simple report containing RLS can help determine whether the problem is related to workspace settings, dataset structure, or the publishing process itself.
Hi @M-IMS ,
The issue of RLS disappearing upon publishing in Power BI can occur due to various reasons, including dataset overwrites, workspace permissions, and inconsistencies in ownership changes. While a change in ownership is a known cause, it is not always consistent, which explains why RLS sometimes remains intact even after an ownership change. If you are the owner and still facing this issue, it could be due to republishing a dataset from Power BI Desktop, which might reset or remove RLS roles if the dataset structure has changed. Additionally, if multiple contributors have access to the workspace, someone else may have modified the dataset, leading to RLS inconsistencies.
Another possible reason is the use of different development environments or shared datasets, where rebinding or reconnecting a dataset in Power BI Service can sometimes reset RLS. To prevent this, ensure that RLS is properly defined before publishing, check if the dataset is being replaced, and reapply RLS settings in the Power BI Service if necessary. Using Deployment Pipelines or version control can help maintain consistency across environments. If the issue persists, testing with a simple report containing RLS can help determine whether the problem is related to workspace settings, dataset structure, or the publishing process itself.
Your RLS issue may stem from one of the following:
Use Desktop to define your RLS, publish, and test. If the issue persists, check the activity logs or open a support ticket.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 58 | |
| 56 | |
| 35 | |
| 18 | |
| 14 |