Hi ARR,
Like mentioned by Steven, it all depends on your current situation. Not only which ISVs are used in AX 2012, but also what type of customizations.
Usually ISV vendors did upgrade their solution to Dynamics 365; taking into account new features where some features from the ISV are now standard in Dynamics 365 or another approach thanks to the new cloud based architecture. There are also some ISV solutions which are not upgraded by the ISV. In that case, you can check for another ISV solution or depending on the licensing terms upgrade the solution yourself.
It is also a good moment for yourself to overthink if you still need all customizations and ISV solutions. If you had e.g. a custom integration with a commerce website, you can now consider using the Dynamics 365 Commerce features. In addition, it could be the case that there is an ISV solution for customizations you had in the past.
You have to keep in mind that you need to stay current with your Dynamics 365 F&O solution. When you have customizations, you need to verify compatibility yourself. An ISV vendor will check compatibility with their solutions for every update from Microsoft. At To-Increase we check every PEAP, first-release and GA releases.
I do hope the reply from Steve and me will help you. If you have specific follow up questions, do not hesitate to ask.
D365 is a generic term that references quite a lot, this is in the AX migration forum therefore the presumption is it is D365FO (Supply Chain and Finance apps).
1. Layers is a concept for AX2012 really, whilst they still exist they do not perform the same functionality. In essence the ISV shifts to extensions, and it is a different approach. The ISV handles this and the impact will be zero on the assumption the ISV is valid on the current D365 version.
2. ISV's are listed on the app store. Customers will use ISV's dependent upon business needs. This in part leads to point 4, you assess your system, what you need, reassess use and new functionality (and deprecated). What you purchased and how you used it may have changed, justify the value of the ISV to move forward and reinvest.
3. What are you looking to overcome whilst upgrading, as this is mainly about ISV's you would need to validate use and then validate your current ISV still exists.
4. This will be the case to many clients, as an example WHS in AX2012 saw many use the Blue Horseshoe solution, Microsoft purchased this and it is now part of the main product, the old WMDP was deprecated and therefore you would need to assess this anyway. It might be you still need the Blue Horseshoe extensions!
This is probably a specific client by client project by project question. I find that many, due to the change in business and requirements aligned to technology see the migration process as a reimplementation ore than an upgrade.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (