Global Branching and Restricted Views - Workaround / waiting time

Ask the Community
1

Hi everyone!

My team and I have been taking advantage of the end to end testing provided by Global Branching. We are very happy with the feature and have found it very useful.

However our ontology objects are backed by restricted views. Restricted views are currently integrated with Global Branching only in experimental phase. Thus we cannot fully test our features, as we cannot add the restricted view to the global branch.

I believe that opting in or out of experimental features is an organization level permission, so I wont be able to simply just use the experimental phase. Thus my options are:

  1. Deal with it (Push schema changes into production without using global branching)
  2. Stop using restricted views in favor of normal datasets (Can the permissions be configured at the object level? Can I fully replicate restricted views capabilities?)

Does anyone know when restricted views for global branching will be available for everyone? Or can anyone answer my second point, as a workaround?

Best regards, David.

2

Hey David!

Unfortunately I don’t know when global branching will be available for everyone.

But, there is an amazing workaround that you can use and that supports branching: object/property security policies. It allows you to handle both row-level and column-level security. The documentation is complete and there is a section about migration from restricted views to security policies.

I hope you find this helpful. Feel free to ask if you have any question.

Nathan :slight_smile:

3

Wow! This looks really good! Thank you very much, how did you find about this?

4

Few month ago, I was looking to a way to handle permissions over my objects properties. I was using multiple restricted views at this moment but that was not really scalable. Then I find this feature, which was in beta, in the documentation.