Dynamics Community Forum Thread Details

Custom API SourceTable property using Purchase Line vs Purch. Inv. Line Aggregate

This all started when I needed to add a custom field, but because the standard api is not extendable, I created a custom api. I had asked earlier about an issue with an error for a POST request for Purchase Lines. I dug a little into the source code for the APIV2 .app source code and noticed they use a different SourceTable than I was. Wondering if that was why I am getting the error? I am using Purchase Header for the SourceTable (this can do my POST request in Postman and set my custom field) and I am using Purchase Line as the SourceTable for my Lines. I noticed in the source code they use Purch. Inv. Entity Aggregate and Purch. Inv. Line Aggregate respectively for the SourceTable in the API. Am I not using the correct SourceTables? Could this be why I am getting my error when doing a POST request for my lines? Here was the error I am getting using SourceTable Purchase Line. Do I need to switch my SourceTable to what the APIV2 .app source code is using instead Purch. Inv. Line Aggregate?

Response:
"error": {
"code": "Internal_InvalidTableRelation",
"message": "The field Document No. of table Purchase Line contains a value (108183) that cannot be found in the related table (Purchase Header). CorrelationId: dcae148f-afbf-4be8-99d8-50fc86a13a3a."
}

Categories:

Dynamics 365 Business Central

Quick Links