create a purchase order from vendor ax 2012

Is there a best practice to choose between these tables? Yes, for sure you have to consider possible performance impact.Ī side example before coming back to the real requirement:

So, the base table to secure would be the Vendor groups table or the Vendors table directly and constrain other related tables. Usually, the vendor groups are used to make this grouping. Note that this option requires development and deployment of a customization.īefore implementing the XDS policy, we have to know how to distinct the employees from the trading partners.

These policies can be creating with help of the Extensible Data Security framework (XDS). An user will get access to a certain menu item, but there will be a constraint on the individual records. In the current Microsoft Dynamics 365 Finance and Operations applications, it would be possible to implement data security policies. This approach will be described more in detail. My initial thought would be hiding all records who are an employee. Now we know the full scenario, there should be a decision whether the purchasing agent would be able to view all vendor records including the employees or just the trading partners.

This will be a recurring attention point in all upcoming scenarios. When designing the security, you always have to take care of securing outgoing cash flows. For sure, you would like to prevent a purchasing agent from changing bank accounts from the employees if they are setup as vendors. the case when you want to be GDPR compliant. In this case, it is not only about the transactions, but also your would like to protect private data like postal addresses or phone numbers. From this form, depending on the rights, the purchasing agent would be able to view the vendor transactions. A purchasing agent usually has at least view access on the vendor form. For example when you implement expense management, it can be used to create balances on the employees and use the vendor payment journal to reimburse the expenses to the employees.

It is quite common to setup your employees as vendor in Microsoft Dynamics. In this particular post, a possible security setup for the next scenario will be explained: “A purchasing agent is not allowed to view employee transactions” Scenario This is the first scenario in a new blog series about “ Security how-to“.

Create a purchase order from vendor ax 2012