Dynamics NAV 2018 API

Business Central/NAV Developers Forum
1

Hi folks!!!

We are working with new Dynamics NAV API… all works well when we do POST, GET, PATCH and DELETE. I’ve created a new Page API for journals, because the standard journal API si very limited (it only allows G/L accounts, and only can read/create/modify/delete, but not posting).

I’ve been searching for a Page API to post a sales invoice… observing current Page API for sales invoice (5475 Sales Invoice Entity), I’ve seen a few functions classified as “External” (visibility) and “ServiceEnabled”. In fact, when I look for API metadata in:

myServer:myOdataServicePort/…/$metadata

The system shows my, all data definitions for the API, including those functions defined as “External” and “ServiceEnabled” in their properties… in the case of sales invoice, I can see 5 actions:

<Action Name="Post" IsBound="true">
    <Parameter Name="bindingParameter" Type="Microsoft.NAV.salesInvoice" />
</Action>
<Action Name="PostAndSend" IsBound="true">
    <Parameter Name="bindingParameter" Type="Microsoft.NAV.salesInvoice" />
</Action>
<Action Name="Send" IsBound="true">
    <Parameter Name="bindingParameter" Type="Microsoft.NAV.salesInvoice" />
</Action>
<Action Name="Cancel" IsBound="true">
    <Parameter Name="bindingParameter" Type="Microsoft.NAV.salesInvoice" />
</Action>
<Action Name="CancelAndSend" IsBound="true">
    <Parameter Name="bindingParameter" Type="Microsoft.NAV.salesInvoice" />
</Action>

The question is: how can I access to these actions? How can I post a sales invoice from API using “Post” action?

2

I found how to do it!!!

You have to do a POST to an invoice ID, following this:

http://YourServer:YourOdataServicePort/YourServiceName/api/beta/[companies(company id)/]salesInvoices(invoice Id)/Microsoft.NAV.Post

“companies” part is necessary if you don’t have a default company in service configuration or you need to post over more than a company.

Be careful with capital letters, write “Microsoft.NAV.Post” this way.

3

Good work finding it out yourself. And you are indeed right this is one very good way of doing it.

You could also just create a new codeunit - with a function ind it as

PostSalesInvoiceNo(InvoiceNo)

SalesHeader.GET(InvoiceNo);

SalesHeader.Invoice := TRUE;

SalesHeader.Ship := TRUE;

IF Not SalesHeaderPost.(SalesHeader) then

EXIT(COPYSTR(GETLASTERRORMESSAGE,1,80);

You then have to remember to make the function in the codeunit PUBLIC.

Something like the above :slight_smile:

4

Hi Palle!!!

I was thinking in other ways to do that (in fact, in my personalized journal API I implemented a method trough a new control in the page and works very well), but I prefer to use the action provided by API… it was very anouying seeing the action and was not able to use it properly!!!

Otherwise, if anyone try to use your example, he has to bear in mind that Sales header has a “Document type”, but the idea is the important thing, and is a good one.

Best regards!!!

5

Thanks for that insight!