Microsoft Dynamics AX (Archived)

XDS Policy - Restrict operations on Purch Line based on PurchTable Data

(0) Share

Report

Posted on by Community Member

Hi all!

Currently I'm having trouble with setting up an XDS Policy correctly.

I want to achieve the following:

Grant Users the right to insert, update or delete PurchLine records when a field in the PurchTable has a certain value.

In Detail I want to achieve that Users are able to add and update new lines in a purch order when the purchpoolid (field in PurchTable, not in PurchLine) has the value "80" or "08".

With my current setup the policy works correct when it comes to update existing purch lines. But when the user wants to create a new line, the system doesn't recognize any restriction by the XDS policy. Users can create new purch lines in every purch order - no matter which value the purchpoolid has. I already tried to set it up using a NoExistJoin for testing reasons. But the behaviour is the same: when it comes to updating records, the policy works fine but inserting new lines is not limited, unfortunately. I added the PurchLine in the policy's constrained tables, though. What did I miss to do here? Or is there maybe the necessity to work with two different policies for covering that requirement?

Thank you in advance!!

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

guk1964 10,888 on at

Like (0)

Report

You are looking at a line level control but isn't the pool at header level?

If so then create filter of all POs for those pools, so the user only sees those related POs then further control is not needed.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi!

Thanks for you fast reply! Exactly, I need to control the PurchLine based on a value in the Header...

I already was thinking about restricting the view to those pools. But unfortunately this is not an option because another requirement is, that the users still have access (reading rights) to POs of the remaining pools.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Please, does anybody have an idea how I can make the policy work not only for restricting updates on existing lines but for restricting inserting new lines as well?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Noone an idea?

Was this reply helpful? Yes No
Verified answer

André Arnaud de Cal... 301,049 Super User 2025 Season 2 on at

Like (0)

Report

Hi FS146,

I was able to reproduce your issue. I also have tried another security policy based on purchase order lines. This is not working for new records on the purchase order lines. I could only, just like you, enforce the policy during updates.

There can be several causes, like application logic but also the kernel interpretation. I haven't searched in detail. As this is not working, you could create an incident for Microsoft Support.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi André!

Thank you very much for having a look at this issue and for your effort in general!

I will try to get in touch with the Microsoft support.

Regards,

Florian

Was this reply helpful? Yes No