API : Request to pass dimensions as a part of the Sales and Purchase Line entities


Dimensions are a key part of the Business Central. However, none of the sales or purchase line entities does contain a complex data type to pass the dimensions. It would be great if the line entities are extended to pass the dimensions just like in "Journal Lines Entity".

Read more...
0 Comments

Read more...
0 Comments

Category: Development (1402)

STATUS DETAILS
Needs Votes

"Notification Entry" to process based on entry status


If there is an error in one of the "Notification Entries", Business Central does not process the rest of the entries till the error is resolved. Would be great if the "Notification Entry" table contains the status of the entry and also the "error message". Then ignore the errored entries during...

Read more...
0 Comments

Read more...
0 Comments

Category: Development (1402)

STATUS DETAILS
Needs Votes

API: New API endpoint for Contacts


In many companies, contact and customer details are maintained in a separate system which is specialized for customer interactions. Therefore in many cases contact is created on a CRM system and then pushed to BC when it is required. Business Central APIs does not have an API endpoint for Conta...

Read more...
1 Comments

Read more...
1 Comments

Category: Development (1402)

STATUS DETAILS
Needs Votes

API : Status to check if the document is posted or not in "Sales Invoice Entity" API


"Sales Invoice Entity" API does bring back data from Posted and Unposted documents. However, receving end of this dataset does not have a way to identify which is posted and which is not. Current “Status” field in the API does not reflect if the invoice posted or not. It is to check if the invo...

Read more...
0 Comments

Read more...
0 Comments

Category: Development (1402)

STATUS DETAILS
Needs Votes