Share
Report
8Hello team,
I am endeavoring to create a custom API for purchase invoices using AL Extension with OData. In this API, I've employed the SourceTable = 'Purch. Inv. Entity Aggregate' as it provides fields such as Vendor Id, Pay-to Vendor Id, among others. However, crucial fields like Posting Description, On Hold, Remit-to Code, Purchaser Code, and others are absent. How can I integrate these additional fields into the Purch. Inv. Entity Aggregate table? Furthermore, how can I utilize them within the custom API code with OData, particularly when invoking the custom API via the POST method, how can I pass those additional properties?
I am endeavoring to create a custom API for purchase invoices using AL Extension with OData. In this API, I've employed the SourceTable = 'Purch. Inv. Entity Aggregate' as it provides fields such as Vendor Id, Pay-to Vendor Id, among others. However, crucial fields like Posting Description, On Hold, Remit-to Code, Purchaser Code, and others are absent. How can I integrate these additional fields into the Purch. Inv. Entity Aggregate table? Furthermore, how can I utilize them within the custom API code with OData, particularly when invoking the custom API via the POST method, how can I pass those additional properties?
Categories:
I have the same question (0)
All responses (
Answers (
