Security checks for Assign and AssignTo should not be run if the field is populated but has not changed from the existing value

Question

Security checks for Assign and AssignTo should not be run if the field is populated but has not changed from the existing value

MattTrinder1 opened this issue 4 years ago · 1 comments

It is possible in code to create an entity object, populate some lookup fields and then save it. The same entity object can then be updated by a different user context which does not have Assign and AssignTo permissions. Dynamics allows this as the field values have not changed, XrmMockup fails.

Answer 1 · 2021-03-05T13:10:31.000Z

Added in 1.7.7