More challenging will be hiding fields that are not directly bound to a table field. In both Microsoft Dynamics 365 and AX 2012, you can achieve it, but there are differences. This is not the most difficult part of the steps you need to perform.

To solve this issue, you need to use table and field permissions. For sure you can think of other reasons to secure individual fields. Some organizations would really like to prevent from leaking information about cost of producing items. If these organizations do approach it correctly, they should also hide any margin amounts or ratios.Īnother reason would be securing company sensitive data. They forget that salaries need to be paid, the office and warehouse rent should be covered, marketing efforts are also expenses and taxes are inevitable. a contribution margin of 25% they think they can give away more discount. The fact is that there are more costs related to running a company than only sales price minus cost price.

One of the most heard reasons is the fact that workers would make wrong assumptions about margins. Scenarioįor many different reasons, organizations do have the requirement to hide cost amounts. This post will explain how to secure fields, form controls, and an easy way to apply this scenario to the users. In this particular post, I will explain how to secure a common scenario where cost amount fields should be hidden for the majority of users. This post is a new blog in the series about “ Security how-to“.

Dynamics ax cost