Tracking content of a Business Central configuration package can help to ensure the packaged data and its setup as per your expectation. Here is a way to do it with some code snippets for process automation.
In the earlier version of Business Central, the only way to copy data between companies was either to copy the company or upload the data through Configuration Packages or Rapid Start.
Microsoft introduced Copy Data from Companies to copy data from specific tables in companies to your respective table in your company.
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.