The chapters below describe the feature set of Extension page.

Setup

Extension Nos. Format	This is the no. series format used when a new extension is created.
Extension File Name Format	Provide the format of extension filenames when objects are added to your extensions. By default OMA uses “Table 3 Payment Terms.al”. To use the format Microsoft suggests “Tab3.PaymentTerms.al” you can enter the following format in the setup: `<Type,3> <ExtendedNumber,Visible=Extension> <'-',Visible=Extension> <'Ext',Visible=Extension><Number>. <Name,Stripped>.al` More info: File Name Format
Generate Symbol Reference	In order to keep your VS Code in sync with your development database you will have to generate symbol reference every time you compile an object.
Update History	Choose how OMA must check if objects or files are changed in you extensions. This setting can be overwritten on the extension card. Automatic – OMA checks automatically if an object/file has changed in your extension and updates the history. Manual – The object/files are only checked if the button Update History is clicked. Selected User – OMA checks the history is the selected user is active. This setting is used if someone has the extension on a local path that other users cannot access.
Update History User	The history is only checked if this user is active.

Add Extensions

The OMA works with two different types of extensions. First the database extensions. The source code of these extension is retrieved from the database and the source code cannot be modified by the OMA.
To add database extensions go to Objects > Extensions > Add Database Extensions > Select all > OK

The second type is the File System Extension. The OMA reads the source code from your AL-files from your hard disk and the OMA can modify these files when you use for example the translation tool or check guidelines.
To add a file system extension go to Objects > Extensions > Add File System Extension > Browse to your app.json > Open

Comments

Comments are similar to Comments in projects.

For more information see Comments Chapter.

Documents

Documents in transports are similar to Documents in projects.

For more information see chapter Documents.

XLIFF

If you work with extensions you can choose to specify your captions in your objects or in separated xliff files.

Working with xliff files is very error-prone. If you change a name, ID, or base caption in your object the link with the xliff caption is lost and the base caption is used instead. It is much safer to keep your captions embedded in your objects and separate them only when you need to. E.g. when you want to publish your extension to the AppSource. To do this you can press XLIFF on the Extension card.

You can perform the following actions:

Captions from Objects to XLIFF – Xliff files will be created in the specified directory.
Captions from XLIFF to Objects – The captions from the xliff files will be placed in your objects.

Enable the checkbox Delete Captions from Objects to transfer the captions to the xliff files and remove them from your objects.

Dependencies

To analyze where references are between your extensions you can press Dependencies on the Extension List. You can add extensions or change the order of the extensions with the buttons in the ribbon. Press Refresh to read the where used base and fill in the references between your extensions.

In the following example, you see all occurrences of the extension “Intelligent Cloud Base” in the extension “Business Central Intelligent Cloud”.

Im- and Export Extensions

Import Extension

To install an app in your database you can import the package file with File Functions > Import File.

The Extension Management page will open where you can install the extension.

Export Extension

To export your extension to an app file you press the Export button on the extension Card. Choose a location and save the file.

Transport Extension

You can send extensions to your customer database through transports.

Add a new project.

Assign the modifications made to the extension to your project.

Beside the objects you have changed also the extension will be added to the project.

Add your project to the transport and press Transport. A new folder for the transport is created with the fib file.

If you import the transport in your customer database with the wizard a step Import Extensions is used to import the extension.

For more information about transport see chapter Transports

Convert C/AL to AL

Beside the option explained in this chapter, the Object Manager has two other options to convert your objects to AL format.

The simplest one is the option Export AL File.. in the Object Explorer.
The most extended option is the Convert C/AL to AL Converters.
The third is explained in the chapter.

To convert your C/AL objects to an extension you select the objects in the Object Explorer and press Convert Objects...

Enter the folder of your extension and a prefix and start id and press Convert.
Your VS Code project will be populated with your objects.

.