- AYes possible
- BNot possible
Time Taken:
Correct Answer:
Wrong Answer:
Percentage: %
Yes possible.
Add indexes to tables through extension
Yes Possible.
Add relations to tables through extension
Yes possible
Learn more: Add methods to tables through extension
Related Topic: Explore extensions and the extension framework in finance and operations apps
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.
Add a new control, enable or disable an existing control, or change a control's visibility.
Creating an index in the same manner as you would add an index to a new table is the correct approach. Creating a unique index using the extension is not allowed because it is intrusive. Adding the index to the base table is incorrect because the new field was added to the extension, not the base table. Using a third-party tool is not recommended because it may not be compatible with Microsoft Dynamics 365.
Defining Classes - Visual Basic | Microsoft Learn
Add a table extension to a project - Training | Microsoft Learn
Wrong: Create a batch job that periodically adjusts inventory levels based on purchase orders.
Wrong: Modify the base inventory class directly to include the new adjustment logic.
Wrong: Use an event handler on the purchase order form to adjust inventory when a new order is placed.
Creating a new class or extending an existing class are both appropriate ways to add functionality without impacting the performance of the system. Modifying the base class directly is not recommended as it can lead to issues during updates and maintenance. Creating a batch job would not be real-time and could lead to performance issues if not managed correctly. Using an event handler on the purchase order form does not encapsulate the logic in a class, which was the requirement.
Extension points for frameworks - Training | Microsoft Learn