Unable to add Purchase Order (PO) number to Pending Vendor Invoice

[rosirsosss]

hello, We are trying to use PA and AIBuilder and pushing vendor invoices into D365. We are successful in reading the vendor invoices and pushing it into D365 - the extracted invoice fields and the invoice preview is visible in "Pending Vendor Invoice" in D365. One thing we are missing is the ability to insert the Purchase order value into Pending Vendor invoice in D365

The approach we used to create the invoice in D365 --> using the PA connector "Fin & Ops Apps (D365)" and Action "Create record" and Entity "VendorInvoiceHeader". This entity does not have a PO number field so we are not able to pass the PO we have extracted from the invoice while creating the invoice in D365.

Is this by design? or should i being using a different entity while creating the invoice? or do i have to add another step in PA to add the PO to the vendor invoice created? Please let me know if anyone has been able to do this.

Note: we are using a trial instance of D365.

After the invoice is created in D365, i am able to manually select the PO number to the invoice.

thank you

[rosirsosss]

Posted the same topic to the Dynamics 365 community (and a few MS friends). They seem to confirm that PurchaseOrderNumber field should be available inVendorInvoiceHeader entity. But this field is not available on the Create Record action when the VendorInvoiceHeader entity is selected.

is this a bug? please check below link - it has screen shots for reference.

https://community.dynamics.com/365/financeandoperations/f/dynamics-365-for-finance-and-operations-fo...

[Expiscornovus]

Hi @rosirsosss,

As a workaround I tried using a POST and Patch via OData:

Open Data Protocol (OData) - Finance & Operations | Dynamics 365 | Microsoft Docs

But I am getting insert not allowed for field error for POST and a update not allowed for field error for a PATCH on the VendorInvoiceHeaders entity.

{
  "error": {
    "code": "",
    "message": "An error has occurred.",
    "innererror": {
      "message": "insert not allowed for field 'PurchaseOrderNumber'",
      "type": "Microsoft.Dynamics.Platform.Integration.Services.OData.ODataSecurityException",
      "stacktrace": "   at Microsoft.Dynamics.Platform.Integration.Services.OData.Update.UpdateProcessor.CreateEntity_Save(ChangeOperationContext context, ChangeInfo changeInfo)\r\n   at Microsoft.Dynamics.Platform.Integration.Services.OData.Update.UpdateManager.<>c__DisplayClass10_0.<CreateEntity>b__1(ChangeOperationContext context)\r\n   at Microsoft.Dynamics.Platform.Integration.Services.OData.Update.ChangeInfo.ExecuteActionsInCompanyContext(IEnumerable`1 actionList, ChangeOperationContext operationContext)\r\n   at Microsoft.Dynamics.Platform.Integration.Services.OData.Update.ChangeInfo.TrySave(ChangeOperationContext operationContext)\r\n   at Microsoft.Dynamics.Platform.Integration.Services.OData.Update.UpdateManager.SaveChanges()\r\n   at Microsoft.Dynamics.Platform.Integration.Services.OData.AxODataDelegatingHandler.<SaveChangesAsync>d__3.MoveNext()"
    }
  }
}

{
  "error": {
    "code": "",
    "message": "An error has occurred.",
    "innererror": {
      "message": "update not allowed for field 'PurchaseOrderNumber'",
      "type": "Microsoft.Dynamics.Platform.Integration.Services.OData.ODataSecurityException",
      "stacktrace": "   at Microsoft.Dynamics.Platform.Integration.Services.OData.Update.UpdateProcessor.UpdateEntity_Save(ChangeOperationContext context, ChangeInfo changeInfo)\r\n   at Microsoft.Dynamics.Platform.Integration.Services.OData.Update.ChangeInfo.<AddAction>b__1_0(ChangeOperationContext operationContext)\r\n   at Microsoft.Dynamics.Platform.Integration.Services.OData.Update.ChangeInfo.ExecuteActionsInCompanyContext(IEnumerable`1 actionList, ChangeOperationContext operationContext)\r\n   at Microsoft.Dynamics.Platform.Integration.Services.OData.Update.ChangeInfo.TrySave(ChangeOperationContext operationContext)\r\n   at Microsoft.Dynamics.Platform.Integration.Services.OData.Update.UpdateManager.SaveChanges()\r\n   at Microsoft.Dynamics.Platform.Integration.Services.OData.AxODataDelegatingHandler.<SaveChangesAsync>d__3.MoveNext()"
    }
  }
}

[natalieroberts]

Hi, I just wanted to comment on this as I was facing the same issue. Our result was to turn off an automatic default setting in F&O and redeploy the environment. This setting I am referring too by default disables the ability to "edit" the invoice header. By changing this to allow editing on creation, we were able to use the field within Power Automate. Hope this can help others in the future. 

[apdemots]

hello @natalieroberts  what setting did you disable for this feature?

[natalieroberts]

@apdemots 

Hi there! There is a property on the data entity, I believe, called "AllowEditOnCreate". This needs to be true or changed to "yes" in order for the PO number to be visible in the API. Hope this helps!