The AL developer preview is still evolving with frequent updates. Follow us on the Dynamics NAV Team Blog for the announcements.
Control Add-In Object
The control add-in object allows you to add custom functionality to Dynamics 365 for Finance and Operations, Business edition and Dynamics NAV. A control add-in is a custom control, or visual element, for displaying and modifying data on pages. Control add-ins can exchange data with the Dynamics 365 and Dynamics NAV server on various data types and can respond to user interaction to raise events that execute additional AL code.
AL tools functionality is supported in Dynamics 365 for Finance and Operations, Business edition and Dynamics NAV, but in some cases, there are limitations. These limitations are marked clearly in the specific topic.
Control add-in properties
In the control add-in definition, you must set the
Scripts property to include scripts in the control add-in. The scripts could be local files in the package or references to external files using the HTTP or the HTTPS protocol. With the
StartupScript property, you can call a special script that runs when the page you have implemented the control add-in on, is loaded. These settings initialize the control add-in.
StyleSheet properties, you can specify additional styling to the control add-in. The layout properties are set to define the size of the control add-in. It is recommended to apply some size to the add-in using these properties. The properties
HorizontalStretch determine how the control add-in behaves in the client when the window it is displayed in is resized. The default value is false which means that the control add-in is not resized vertically, or horizontally. The value
true means that the control add-in is resized vertically, or horizontally. The values set by the
RequestedWidth properties determine the minimum resize value of the control add-in. Read more about the sizing of control add-ins in the next section.
Sizing of the control add-in
To control that the sizing of the control add-in is always optimal, even on smaller display targets, such as the phone, some settings are available when you write the control add-in. The settings make sure that resizing of the control add-in works on all client types.
||Boolean||Specifies that the control add-in can be made smaller vertically. This setting is optional.|
||Boolean||Specifies that the control add-in can be made smaller horizontally. This setting is optional.|
||Integer||Specifies the minimum height that the control add-in can be shrunk to. This setting only applies if the
||Integer||Specifies the minimum width that the control add-in can be shrunk to. This setting only applies if the
||Integer||Specifies the maximum height that the control add-in can be stretched to. This setting only applies if the
||Integer||Specifies the maximum width that the control add-in can be stretched to. This setting only applies if the
||Boolean||Specifies that the control add-in can be made larger vertically. This setting is optional.|
||Boolean||Specifies that the control add-in can be made larger horizontally. This setting is optional.|
||Integer||Specifies the initial height of the control add-in.|
||Integer||Specifies the initial width of the control add-in.|
Control add-in syntax example
The following control add-in example syntax defines a chart that can show how customers are represented per country on a map. The control add-in is implemented as a
usercontrol on a page called CustomersMapPage.
AL Development Environment
Asynchronous Considerations for Control Add-ins
Page Extension Object
Page Customization Object