One of the most popular tools in Microsoft Dynamics 365 Business Central is Configuration Packages. In this article we will cover the basic and advanced features of this tool.
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.
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.
A great way to make your customizations or your app more user-friendly is to generate configuration packages. Removing the stress for users of figuring out what tables go into a package.
In this video, I show how easy it is to create the configuration package definition in AL.
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.