61
It would be helpful if Business Central had the ability to hide specific fields from specific users. For example, recently we had a request to hide the Unit Cost field from the sales team. However, the sales team needed access to the Item table to view other item information. Since security in Business Central is at the table level there was no out of the box way of handling this. This specific request has been very common throughout my career, but there are many different applications of needing to hide specific fields from specific users. We ended up creating an extension and having to locate every page the Unit Cost (and other cost related fields) is on, and hide it if a user was assigned to a "HIDEUNITCOST" permission set.

I know in NAV 2015 Microsoft introduced functionality called AccessByPermission that allowed for the ability to hide fields at the table level which would make this process much easier. However, this functionality has not been made available in Business Central. In summary, it would be helpful if Business Central had an out of the box way to perform field level security/visibility.
Category: Development
STATUS DETAILS
Declined
Ideas Administrator

Thank you for your feedback. We are not considering the suggestion at this time due to the following reason: This is already possible to implement using indirect permissions. We will update the docs with more clarity on how to do that.

Sincerely,

Kennie Nybo Pontoppidan

PM, Microsoft

Comments

M

We would need something that an End User can modify. An Extension/customization to update every page isn't realistic.

Category: Development

M

I agree that can be done through development but highly voting to have that option by default, it's impractical to just assign a developer to do these things.

Strongly voting to add this feature ASAP.

Category: Development

M

Show/hide per user permissions
Editable per user permissions
Development on full ERP solution is not a option and MergeTool EasySecurity is not an option 2019 Fall wave 2 and forward because it does not support ISVs.

Category: Development

M

You can do this, but it requires development (an extension). If you set the Visible property on fields (such as Unit Code) to a variable (eg. gblnShowItemCost) and then add code to the OpenPage action (using event subscriptions) to the pages that show the unit cost (to set the variable based on user setups), the field can be hidden. It would be much better if there was a property for this at the table level...for now you need to modify the various pages that show Unit Cost.

Category: Development