Summary
Creating extensions can be a simple process to help customize the finance and operations apps user interface. Because finance and operations apps are provided as an Infrastructure as a service (IaaS) application, updates are made regularly. Overlaying base code can cause update conflicts and issues and can create extra work for developers. Extensions often save you money because you don't have to spend time fixing overlayered code that broke during an update.
For these reasons, overlaying is not allowed in finance and operations apps, and extensions are the preferred practice for customizations.
Elements within the AOT, such as EDTs, enums, tables, and forms can be extended and added to your project. You can also create an augmented class to use code to customize finance and operations apps. If creating an extension doesn't fulfill your customization needs, you can log an extensibility request with Microsoft through your project in Lifecycle Services.
Links to related modules (and sites) for specific topics
| Topic | Link |
|---|---|
| Extensibility | Extensibility home page |
| Submit request for new extension points | Extensibility Requests |
| How to avoid intrusive customizations | Intrusive customizations |
| Extensibility roadmap | Application extensibility roadmap |
For further information about extensions, advance to the next module in this learning path about extending elements.