How To Use the Configuration Package to Update Standard Cost in Microsoft Dynamics 365 Business Central and Dynamics NAV

In Microsoft Dynamics 365 Business Central or Dynamics NAV, typical processes for updating the standard cost for a purchased item are as follows:

– For a new purchased item, the standard cost can be updated on the Item Card.
– For a purchased item that already has ledger entries, the revaluation journal is used to populate the entries and re-value the cost.
– For a manufactured item, the Standard Cost Worksheet is used.

Source : ArcherPoint
Read more…

Dynamics 365 Business Central: How to use Configuration Package to post documents (Sales Order, Purchase Order, Transfer Order, General Journal, etc.)

When importing the opening balance to Business Central by Configuration Package, you cannot import the posted data directly, such as Posted Sales Invoices, Customer Ledger Entries, General Ledger Entries, etc., so you should first import the data before posting, such as Sales Order, General Journal, etc., and then do Post from the page. This is a very common practice.

Source : Dynamics 365 Lab
Read more…

Dynamics 365 Business Central: loading Configuration Packages from AL (part 2)

More than one year ago I wrote this post on how to import directly from AL code a Configuration Package (.rapidstart) file.
This code uses the ImportRapidStartPackageStream method declared in the “Config. Package – Import” codeunit as follows:

Source : Stefano Demiliani
Read more…

Introducing a build version check between NST and Windows and Web clients

Have you ever wonder what ‘The client version does not match the server version. You can only connect to a server with a matching version.’ error message really means? Since the error message shows the file (build) versions of the client and server it has been speculated that only clients and servers of the same build can connect, which is not the case. What really happens is that we have a communication interface between Microsoft Dynamics NAV Server and clients that has an internal version number which we change when this contract is broken (interface is changed so that it is not compatible anymore), and in that case the versions will not match and you will receive this error.

Bron : Microsoft Dynamics NAV Team Blog
Lees meer…