You need to modify the environment to meet User1’s requirements. What should you do?

The correct and supported method for adding a new field to a standard table, such as CashDisc, in Dynamics 365 Finance and Operations is to create a table extension. This is done within a new or existing project that belongs to your custom model. By creating an extension, you add the new field to a separate object that augments the original table at runtime. This extension-based approach is fundamental for maintaining upgradability, as it isolates your customizations from the standard application code, preventing them from being overwritten during system updates.

B. Creating a new table is an incorrect approach. It does not modify the CashDisc table but instead creates a completely separate data structure.

C. You cannot use the designer to directly add a field to a standard, sealed table. The designer will not permit modifications; you must first create an extension.

D. Overlayering standard Microsoft models is deprecated and has been sealed, making it impossible. All customizations to standard objects must be implemented as extensions.

1. Microsoft Learn. (2023). Extend tables - Finance & Operations | Dynamics 365. Retrieved from https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/developer/extensibility/extend-tables.

Reference Point: The "Table extensions" section explicitly states, "You can add new fields... to a table by creating a table extension." This directly supports the correct answer (A).

2. Microsoft Learn. (2023). Create table extensions - Finance & Operations | Dynamics 365. Retrieved from https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/developer/extensibility/create-table-extensions.

Reference Point: The tutorial outlines the exact steps: "In Application Explorer, find the table that you want to extend... Right-click the table, and then select Create extension." This confirms the process in option A and shows why option C is incorrect as a standalone action.

3. Microsoft Learn. (2023). Customization: Overlayering and extensions - Finance & Operations | Dynamics 365. Retrieved from https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/customization-overlayering-extensions.

Reference Point: The section "Why is overlayering restricted?" states, "Microsoft has sealed the Microsoft models... you can't overlayer the objects in them. Instead, you must use extensions to customize the application." This directly refutes the validity of option D.