Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming 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