Extension

We can Modify existing fields in a table through extension

Yes Possible.

Yes possible.

Yes Possible.

Yes Possible

Yes possible

Yes Possible Learn More: Modify the properties of form controls through extension

Yes possible Learn More: Add data sources to forms through extension

Yes Possible

Justification

• A. Incorrect: Extensions can take longer to create than overlaying elements.

• B. Correct: Build and compile times are reduced with extensions because you don’t have to compile the model that is being extended.

• C. Incorrect: Microsoft rolls out updates more frequently and quickly when using extensions.
• D. Incorrect: Extensions in many cases cost nothing to maintain because updates aren’t likely to cause any issues.

Related Topic: Explore extensions and the extension framework in finance and operations apps

Justification:

• A. correct: The IsExtensible property of the enum must be set to True to be able to create an extension.
• B. Incorrect: Not every enum in Visual Studio can be extended. The IsExtensible property must be set to True and you must be referencing the model that contains the enum.
• C. Incorrect: Enums that are contained in other models can be extended if the IsExtensible property is set to True and you're referencing the model that contains the enum.
• D. Incorrect: The IsExtensible property for the enum must be set to True, not False, to be able to create an extension of that enum.

Related Topic: Explore extensions and the extension framework in finance and operations apps

Justification:

• A. Incorrect: While it's best practice, it's not necessary to sync database on build to create extensions.
• B. Correct: To create an extension of an element, you must verify that you're referencing the model in which the element resides.
• C. Incorrect: Setting the AOT to Model view or Classic view is personal preference. This won’t affect your ability to create an extension.

Related Topic: Explore extensions and the extension framework in finance and operations apps

Answer: A

Extension-based development is the recommended approach for developing finance and operations apps. This approach allows developers to add functionality to existing model elements and source code without having to modify the base code. This makes it easier to customize and update finance and operations apps to meet the specific needs of businesses.

Overlayering-based development is an older approach to developing finance and operations apps. This approach involves modifying the base code of the app. Overlayering-based development is less flexible and more difficult to maintain than extension-based development.

Legacy development is a term used to describe the development of finance and operations apps using older technologies and approaches. Legacy development is not recommended for new development projects.

Creating an extension of a form is the best way to add new functionality to a form in Finance and Operations. Extensions are collections of changes to existing model elements, such as forms. They can be used to add new fields, modify existing fields, or add new controls to a form.

Extensions have a number of advantages over other approaches to adding functionality to forms, such as modifying the base code or creating a new form. Extensions are:

• Extensible: Extensions allow you to add new functionality to forms without having to modify the base code. This makes it easier to customize and update forms without having to worry about breaking the base code.
• Flexible: Extensions are very flexible. You can use extensions to add any type of functionality to a form, from simple changes to complex business logic.
• Maintainable: Extensions are easy to maintain. You can easily modify or remove extensions without affecting the base code.
• Upgradable: Extensions are easy to upgrade. When you upgrade your Finance and Operations environment, your extensions will be automatically upgraded as well.

Add a new control, enable or disable an existing control, or change a control's visibility.