Microsoft Dynamics 365 F&O or Microsoft D365 for Finance and Operations product range will be on the same update cadence. Depending if you are already running Microsoft Dynamics 365 for Finance and Operations or not there are changes which you also need to prepare for yourself. All Microsoft Dynamics 365 customers will run on the same D365 finance and operations version and code base in the coming year.
This means from Microsoft point of view it’s still possible to have own customization’s and ISV solutions in your own environment. The standard application will be the same for all customers.
In the coming year, the Microsoft Dynamics 365 F&O product version number will be 10.0. In between there will be continuous updates for the platform, application and financial reporting fixes as well as the smaller functional features and the regulatory requirements.
Version number 9 will be skipped for Microsoft Dynamics 365 for Finance and Operations. Some more detailed information will be made available soon by Microsoft.
If you are running on previous versions of Microsoft Dynamics AX 2012 or before, this will not directly have an impact for you. However, if you are considering moving to Microsoft Dynamics 365, the information which is provided to all of us is also important for you.
- If you are already running Microsoft Dynamics 365 for Finance and Operations and you are on version 7.3 or below, the product will be considered as end of service.
- Also the service will end for Microsoft Dynamics 365 F&O version 8.0. Microsoft is suggesting to move to version 8.1 as soon as possible.
- If you are already on Dynamics 365 for operations version 8.1, then you are already enrolled in the continuous update plan.
- The Microsoft Dynamics 365 F&O 10.0 version will be an update when coming from this latest version; not an upgrade.
- If you are running on Microsoft Dynamics 365 F&O version 7.3, then in general you also have to be on version 10.0.
By chance if you miss extension points, you need to log extensibility requests. If the extension requests are not submitted , you are expected to have no issues for upgrading and your Dynamics 365 for operations 7.3 environment will be considered as end of service.
Microsoft Dynamics 365 for Finance and Operations exclusively uses the extensions to customize the product. Microsoft Dynamics 365 for Finance and Operations is extensively customized by partners, value added re-sellers (VARs), and even some customers.
The move to the cloud for Dynamics 365 for operations, together with more agile servicing and frequent updates, requires a less intrusive customization model, so that updates are less likely to affect custom solutions.
This new model is called extensibility and has replaced customization through over-layering. If you discover a customization that you cannot implement as an extension, you must log a request to Microsoft to ensure an appropriate extension support is added to the product for your scenario.
Extensibility requests are logged using a specific project in the 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 the requests for a specific solution or an implementation. Microsoft then further identifies the logged requests by the organization name that is associated with the LCS account.
- In your Life Cycle Services project, at the top of the page, select the hamburger icon and then select Support menu item.
- You can see the list of logged extensibility support requests and their status. Click the request ID to review the details of the logged request.
- New requests that are logged, are 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 as Active.
- When a request is processed by Microsoft, the status of the request will be updated as Closed.
- Click the request ID to view the resolution date and description information.
- Requests that have been closed are released with the monthly application updates.
The Extensibility support request form includes two actions:
- Manage extensibility options
- Create extensibility support request
Manage Extensibility Options
When you select 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 the requests can be made to be available for your development. The Extensibility support options can be updated to reflect any changes after a request is created.
Create Extensibility Support Request
‘Create extensibility support request’ is utilized 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 the information on what it is you need to extend.
This will help Microsoft to be efficient in addressing the requests. You are welcome to provide 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 the requests. Each request type changes the form to include the specific fields related to the request type.
Being a Microsoft Dynamics Partner Locus IT understands the unique requirements of Dynamics 365 for operations industry and the particular challenges that currently exists in that industry. For more information on how Microsoft Dynamics 365 for operations can help your organisation, please contact us.