Hi,
I have a dataset designed originally in new UI. Then I applied RLS to it. Everything ran well until I have to update the query. After I updated the query, I couldn’t save and publish. This error showed up
Can I know the reason? and how to fix it?
Hi @baduong,
Since the warning is mentioning that these fields are in your rules dataset but not in your ‘output’, it seems to me like the system is not picking up that these will be the fields you’re basing your restrictions off of.
I encountered a similar issue recently when setting one up, in my instance, it turned out that the field name had to be case sensitive. So I changed my field to ‘UserName’ instead and it worked properly.
I would suggest trying the same with both of the fields listed and see if that works.
I duplicated the dataset and tried the same process but with old UI, there is no issue at all
Hi @baduong,
I’m not quite sure why it works in the old version but not the new version; however, referring to this page, it’s noted that the fields and values are case-sensitive:
When I tested out, I set the field name as ‘Username’ and the RLS did not work correctly. After updating to ‘UserName’, it started working for me.
If the old version is working, I would suggest keeping with that for the time being while they continue to add some of the other missing features to the new data prep experience.
Just so you know, once you switch to the new UI, there’s no going back. So if anyone reading this has the same problem, your best bet right now is to make a new dataset in the old UI and swap it into your analysis.
