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 :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Applying XDS on a sales order

(0) ShareShare
ReportReport
Posted on by 122

Hi. I recently applied an XDS policy on SalesTable to display the sales orders based on the SalesTaker as the current user only and assigned it to a particular role. 

This works great but we have the scenario where a particular employee needs to go on vacation and he needs someone else to handle his sales orders, invoicing etc. 

So we need to be able to assign a user with the security rights to view/access the sales orders of another salesperson along with his own. 

What would be the best way to tackle this scenario? 

  • Suggested answer
    atajjo Profile Picture
    509 on at

    You could edit your policy so it would need only one of the two sales fields (taker or responsible) to be the current user. This way you can assign access to two different people to the same order. One will be taker and the other will be responsible.

    Or you could ask the person on vacation to change the sales taker to someone else. But if you go with this solution, the person on vacation will lose access.

  • André Arnaud de Calavon Profile Picture
    308,205 Super User 2026 Season 2 on at

    Hi Vijay,

    You can check the suggestion from Abdullah or create a delegation table. Then change the XDS policy. You can add a "MyConstruct" table which would add details to a temporary table which can be used as input for an XDS query. The temporary table can be filled with an XDS method on the "MyConstruct" table. You can then use x++ logic to insert a record with your own user or also users for which you are a delegate.

    You can check some of my blogs for looking at different fields for the user ID (suggestion from Abdullah) or using a "MyConstruct" table:

    Extensible Data Security examples - Secure by project responsible (dynamicspedia.com)

    Extensible Data Security examples - Secure by warehouse (dynamicspedia.com)

  • VJ VM Profile Picture
    122 on at
    [quote user="AT982020"]

    You could edit your policy so it would need only one of the two sales fields (taker or responsible) to be the current user. This way you can assign access to two different people to the same order. One will be taker and the other will be responsible.

    Or you could ask the person on vacation to change the sales taker to someone else. But if you go with this solution, the person on vacation will lose access.

    [/quote]

    Yes, currently my policy applies only to SalesTaker. The issue with this is we have SalesTaker and SalesResponsible both filled in as the same user presently. The user also requires to view older sales orders, so I'd have to go back and change the sales responsible / sales taker one by one for all previous orders. 

  • VJ VM Profile Picture
    122 on at
    [quote]

    Hi Vijay,

    You can check the suggestion from Abdullah or create a delegation table. Then change the XDS policy. You can add a "MyConstruct" table which would add details to a temporary table which can be used as input for an XDS query. The temporary table can be filled with an XDS method on the "MyConstruct" table. You can then use x++ logic to insert a record with your own user or also users for which you are a delegate.

    You can check some of my blogs for looking at different fields for the user ID (suggestion from Abdullah) or using a "MyConstruct" table:

    Extensible Data Security examples - Secure by project responsible (dynamicspedia.com)

    Extensible Data Security examples - Secure by warehouse (dynamicspedia.com)

    [/quote]

    Hi Andre. Thanks for getting back to me and sorry for the delay in responding. I cannot change Sales Responsible and Sales Taker, both should be the same person since these have been used interchangeably in many reports. After discussion with the team, it seems I will have to apply the XDS policy to each staff as a role or duty because I'll need to manually assign the salesman's access to another person based on requirement. Also, when I do an assignment like this, the previous salesman's sales orders should be available for the salesman it is assigned to. We also have only a few staff so creating a role for each person is not tedious if it gives me the functionality to switch the user access easily from security configuration. So the question is, if I were to create a query and use WorkerSalesTaker as a range, what would be the value of the field WorkerSalesTaker? Would it be the UserID or name of the employee?  

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 274 Super User 2026 Season 2

#2
Aayush Tiwari Profile Picture

Aayush Tiwari 219

#3
Subra Profile Picture

Subra 202 Super User 2026 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans