Permission By Field (hiding particular fields from viewing and filtering)

dimanop

Hi there,

I have a Page that's based on a large table containing some sensitive information that I don't want certain users to view/filter on.

How do you do this?

I attempted this by using the Access By Permission property behind the relevant field.

I tried setting up a bogus Page that particular users does not have access to. I then attached this Page to the Access By Permission property behind the field I don't want these users to view/filter on.

I made sure that on the Admin console the UI Elements Removal is set to LicenseFileAndUserPermissions.

This doesn't seem to work. Is there anything I'm doing wrong, or is there another way of doing this. Thanks.

dimanop

Just a further note, this is in NAV 2015. Cheers.

Kishorm

A couple of thoughts...

1) Have you checked that the user(s) do not have access to the permissions you have set in the AccessByPermission property?

2) Have you restarted the NST after making the change to the UI Elements property?

As an alternative you should consider storing sensitive data in a separate table (& encrypting it) - have a look at how this is done in standard NAV (filter on objects '*Payment Credit Card*')

Remco_Reinking

If this data is about prices or amounts, you could think about an addition in the AutoFormatTranslate() function in CU 1. Use a different AutoFormatType for your tables and return *** if it should be protected, but only if it is applicable for the current user.

dimanop

Thanks for your replies. It seems the issue isn't hiding the field - even though the field is hidden, you are still allowed to filter on it, as well as choosing it as a dimension and/or measure on the 'Show As Chart' facility.

Kishorm

@dimanop - did you see my comment above about storing it in a separate table and encrypting it similar to Paymenet Credit Card in standard NAV? This will stop the users from being able to filter on it or use it to show as a chart.

dimanop

Storing the information in a separate table is not a feasible exercise in this situation.