Extensibility requests

Finance and Operations applications exclusively use extensions to customize the product. We're aware that this change impacts our entire partner ecosystem. We recommend that you read the resources listed on the Extensibility home page. These resources answer many questions and prepare you for building solutions using extensions.

You'll discover that some customizations, which were possible with overlayering, can't be done through extensions. To enable the same business requirements without overlayering, we have added many extension capabilities and expect to add more going forward. For some customizations that were done with overlayering, you need to log requests, to make us aware of what you need.

What we are doing

In future releases, we'll be adding even more extensibility capabilities to enable independent software vendors (ISVs) and value-added resellers (VARs) to deliver complete business solutions. We'll prioritize these on a customer-by-customer basis with frequent releases.

How do I log extensibility requests?

If you discover a customization that you can't implement as an extension, you must log a request to Microsoft to ensure appropriate extension support is added to the product for your scenario.

Before logging the request, there are a few things to consider:

• Could the requirement be met with existing extensibility features? Building solutions with extensions requires different design and implementation patterns.
• How important is the requirement to the customer and/or business analyst?
• Will the implementation be upgrade friendly for the long term?

For more information about extensibility, see Extensibility home page.

Extensibility requests are logged using a specific project in LCS. Logged requests are collected under that same project. We recommend that you log related requests under the same LCS project as this helps maintain a holistic view on all requests for a specific solution or an implementation. Microsoft then further identifies logged requests by the organization name that is associated with the LCS account.

In your LCS project, at the top of the page, select the hamburger icon and then click Work items menu item.

You can view the list of logged extensibility support requests and their status. Click the request ID to review details of the logged request.

New requests are briefly assigned a status of Pending while the request is copied to the Microsoft tracking databases. Next, an ID is assigned to the request and the status is updated to Active. When a request is processed by Microsoft, the status is updated to Closed. Click the request ID to view resolution date and description information. Requests that have been closed are released with monthly application updates.

Note

At this time, there is no state available to indicate feedback from Microsoft on when requests have been planned.

The Extensibility support request form includes two actions:

• Manage extensibility options
• Create extensibility support request

When you click Manage extensibility options, you can view all of the information that is shared between requests. This information includes, requests for either an ISV or VAR solution and if the requests are specific for a Customer implementation project. If the role selected ISV or VAR, a solution name must be specified. The name should be recognizable and correlate with AppSource solutions. The Required by date indicates the last date that requests can be made to be available for your development.

Important

Microsoft doesn't guarantee that all requests will be provided by the date given. The required date provides an indication that will be considered when planning for requests at Microsoft.

Extensibility support options can be updated to reflect any changes after a request is created. After you have made your updates to the request, click Update to notify Microsoft of your changes.

Note

There is currently no option with the tool to record what a customer implementation includes regarding ISV or VAR solutions.

The action 'Create extensibility support request' is used for creating, or logging, new extensibility requests. When you log an extensibility request, provide detailed information about what you need to become enabled for extensibility, and include information on what it is you need to extend. This helps Microsoft to be efficient in addressing your requests. You can propose how Microsoft could enable the functionality that you need in the standard application in a way that effectively addresses your needs.

When you select the request type, determine how your request aligns with the request types that Microsoft uses to categorize requests. Each request type changes the form to include specific fields related to the request type. This helps guide the process to make the request actionable for Microsoft. Be sure to provide accurate names when naming elements and methods. Microsoft rarely enables requests by adding inline delegates, consider other types of requests. Common application request types include extract method, extensible enum, construct with throw, and method change. Additionally, there's platform request and metadata change for proposing changes, including general platform improvements. The request type method signature change is typically for a breaking change. It's unlikely that a breaking change can be accommodated under a monthly update as it requires a more major release version to drive such changes.

Click Attach file from computer to upload documents that you can attach to requests. You can use the attachments to supply code snippets that provide additional details for the request. We recommend that you be as specific as possible with your requests.

Log a request for each instance. Don't bundle multiple requests into one. If multiple requests are related, consider adding a document or description that includes request ID's so that any work on the requests is considered in context.

The requests include a point of contact. This is needed when the logged extensibility request isn't actionable. The requests may require discussion regarding, for example, different design options. Microsoft uses this contact information to drive such interactions. Click Submit when you're ready to submit the request to Microsoft. Requests can’t be edited after they're submitted, verify the data before you submit. Requests that are accidentally submitted with incomplete or inaccurate date can be removed using the designated action after clicking the ID on the request. Requests that are submitted to Microsoft temporarily show as Pending until the request is created within the Microsoft tracking databases. This assigns an ID to the request and the state becomes Active. This status indicates that the request is now visible to Microsoft.

Make sure to read through the privacy statement before you log any requests.

Note

We will not release extensibility requests as hotfixes. 

Extensibility requests are exclusive for the application. We're not planning to accommodate extensibility requests for Dynamics AX 2012 or earlier releases.

When will my extensibility requests be enabled?

Extensibility requests are logged to a backlog. Microsoft engineers prioritize all requests, and then work on them in priority order. Microsoft doesn't ensure all requests will be fulfilled. In particular, requests that are intrusive by nature won't be supported, as they'll prevent seamless upgrade.

Still have questions?

Read the Extensibility FAQ and the other resources listed on the Extensibility home page.