Suggested by Ibrahim ElGamal – New
The data entity Purchase Requisition V2 is not usable for dual write or integrations because of validation if the worker (Preparer) is equal to the worker assigned to the user.
when you use dual write or oData to create a record, you will use an app registration. This app registration has in Dynamics 365 FnO a (generic) user connected. But this user doesn’t have a worker assigned. You want to populate the Preparer with each worker that exist in the legal entity.
The data entity validates if the worker assigned to the user is equal to the worker specified in the field “Preparer”. From a data management perspective this is very logic. You don’t want that another worker requests a purchase on your name. But from an interface perspective (oData, Dual write) this is not possible. Those will use an app registration that is related to a user that has no worker assigned. Even if you assign a dummy worker to the user, you don’t have the traceability who created the purchase requisition in the external app.
As a workaround:
Extended the Purchase requisition entity and customized the field "preparer" by disabling it's validation
Summary; This validation should only be executed for the Excel add-in or data management. But not for Dual Write or oData.