Dynamics 365 Business Central: How to build extension (Package/Publish) without generating report layout files??? – (“al.compilationOptions” -> “generateReportLayout”)

Today I would like to share a mini tip of Business Central, how to build extension (Package/Publish) without generating report layout files in VS Code.

When we create a new report, there are two main tasks to consider. First, we define the report dataset of data items and columns. Then, we design the report layout.

Source : Dynamics 365 Lab
Read more…

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…

How Do I: Set the runtime version of the extension package?

Recently, on some of my ‘machines’ I get the following errors, when trying to publish an extension (F5):

The runtime version of the extension package is currently set to ‘2.0’.
The runtime version must be set to ‘1.0’ or earlier in the app.json file
in order to install the extension package on this platform.

Bron : Think about IT
Lees meer…