Limit Access on QVD for different developers.

[Maminuli]

I have a use case for which I am looking for a solution. Please let me know in case you can find one.

So let’s say a QVD is created by a admin user. This QVD is having 10 columns.
There are 2 developers – DevA and DevB. These developers are developing two different reports using the same QVD file.
Now because of some operational restrictions, requirement is such that DevA should have access of just five columns – ColA, ColB, ColC, ColD, ColE
and DevB should have access to remaining 5 columns ColF, ColG, ColH, ColI, ColJ.

[Or]

Create two separate QVDs and manage the permissions on those as required. 

[vincent_ardiet_]

If they don't have access to the loading script, you can use the section access with OMIT to do this.

[Maminuli]

Is it possible to give section access on QVD level ?

[PrashantSangle]

No. You cannot. I think what @Or  suggested, you go with that approach.

or

restrict those users add table level in Database only. So your developers will create connection with there id and they will see table and data which is relevant to them only.

Regards,

Prashant Sangle

[Maminuli]

Ok Prashant.

[vincent_ardiet_]

If the developers do not have access to the script, and if your building it for them, you can use a section access with using OMIT to hide the fields.
The security is not at QVD level but in the application.
If you cannot implement a security at database level as suggested by Prashant, you can also create 2 separate QVDs, located in different folders, and gives 2 different data connections to your developers. In this case the 2 files can have the same names.