Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We are using a MapQuest integration with Field One in Dynamics 2011. Recently there was an update from MapQuest about retiring their current version effective June 5th, 2018 and we need to move to Mapquest.js v.1.2.0 to continue using maps with Field One. Initial analysis suggests the new Mapquest.js v.1.2.0 is not compatible with Field One in Dynamics 2011.
Any help on the above will be appreciated.
Thank you for the support.Dama Davis
We are facing exactly the same issue. Would be interested in any solution that is available.
As you're out of support with Microsoft anyway, you might need to have someone customize your FieldOne instance to support the new MapQuest JS. I would warn you that doing so is unsupported, but you're already in an unsupported configuration, so it doesn't really matter.
Your other alternative would be to plan a migration to D365 Field Service.
Or both, first the patch to keep you going and then the migration, since clearly the patch will break at some point in time.
Thank you for the quick update. We are interested in customizing our FieldOne instance to support the new MapQuest JS, but the issue is we do not have access to any API's / custom liberaries of feildone to customize it. Is there anyway someone can direct us to that?
Thank you for the support.
Business Applications communities