web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / How to restrict a user...
Microsoft Dynamics AX (Archived)

How to restrict a user to see his created purchase orders only? AX 2012 R2

(0) ShareShare
ReportReport
Posted on by Rana Anees 1,813

Hii,

On "All purchase orders" form we want that,

If user A has created five purchase orders, then user A should see his created five purchase orders only and not of other users po's.

But the manager of user A should be able to see user A purchase orders and other subordinates.

And CEO of the company should be able to see all purchase orders. Same requirement for Sales Orders.

Please guide how we can achieve this? Do we need customization and how?

Thanks,

*This post is locked for comments

I have the same question (0)
  • Sohaib Cheema Profile Picture
    Sohaib Cheema 49,679 Super User 2026 Season 1 on at

    bit hard but 100% doable.

    use security policy. create your custom setup based on managerial hierarchy and enable createdby on PurchTable(if not already)

    Develop a single security policy and enable it.

  • Rana Anees Profile Picture
    Rana Anees 1,813 on at

    Hii Sohaib Cheema,

    Can we achieve this by Filter records in a Form .. as explained in the following post.

    community.dynamics.com/.../how-to-filter-records-in-a-form

    By following this article..

    In our case PurchTableListPage form has one query and two tables as data sources.

    1. PurchTableListPage - a query - I am unable to add / overwrite method and Range because  add / overwrite option not coming.

    2. PurchTable - table - can't add new methods in this datasource.

    3. VendTable - table -  can't add new methods in this datasource.

    cant edit the query in AOT. Maybe datasources on PurchTableListPage  form are disable from modification as i am ax admin.

    Any idea in this regard.

    Thanks,

  • Suggested answer
    Vilmos Kintera Profile Picture
    Vilmos Kintera 46,149 on at

    Filtering and query ranges is not a good solution, because there are ways around that. As Sohaib has mentioned, you need to involve an AX developer and do a customization using the security framework, with which you could reliably filter out the records that your users should not be able to see.

    My choice would be implementing a custom xds() method to put together the filtering based on the managerial hierarchy, this is point 3) in the following article:

    blogs.msdn.microsoft.com/.../best-practices-tips-and-tricks-for-implementing-xds-extensible-data-security-policies

    The linked article also has a whitepaper which explains such security development in detail.

  • Vilmos Kintera Profile Picture
    Vilmos Kintera 46,149 on at

    Please take your time to verify answers by ticking the checkbox next to each helpful answers in order to close the topic and assist other users with similar problems.

  • Suggested answer
    guk1964 Profile Picture
    guk1964 10,888 on at

    As always your specific situation influences whether a solution make sense.  Without understanding the reason for the requirement its easy to give the wrong advice. Consider:

    Is there also a restriction on what items/categories each user can buy?

    How many buyers/managers are involved?

    How static are the rules? how often do users and managers change ?

    How many POs does each create daily/monthly?

    How does this knock on to reports?

    Is the desire to filter to just make finding a PO easier, or is there a genuine security concern that users should not see the other users data?

    What about those receiving POs or matching invoices -are they more trustworthy with data?

    Will it only apply to PO screen? e.g will a buyer be allowed to see AP screens or Arrival screen?

    Who can see what planned orders?

    How do you stop 4 users each buying the same item  on the same day/?

    Filters are just that -you can set up a filter by Byr /Byr grp but that will not stop someone removing the filter.

    If you code it via xds then beware of performance - it should not be too bad  if its just a user id check at PO header level - but even then the system still has to filter  all the pos in the system.

    If you set this up then think about data/code maintenance e.g. if someone  leaves, or reporting hierarchy changes, etc.

    Don't go live with it without some serious stress testing and user feedback on whether it makes life easier or harder.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 26

#2
imran ul haq Profile Picture

imran ul haq 8

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 4 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans