Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Field Service updates!Learn about the key capabilities and features of Dynamics 365 Field Service and experience some of the new features.
Download overview guide | Watch Field Service video
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
Some needed workflows that were previously published are since the upgrade unpublished and most field service related processes, for example booking resources, booking workorders, planning workorders, don't work anymore. A workaround is to just enable them but why is this? What could be the issue here?
Thanks in advance for a hint or at best solution to the mentioned issue
From which version you have upgraded to 8.X?
Usually it's not happening.
I’ve seen this occur in some circumstances. What version did you upgrade from?
I did update from 7.5 and did the whole upgrade process again with a tiny difference. I reassigned all records of a deactivated system administrator (the guy who set everything up and left the company so we got a new admin account) to ours and there is only one business process deactivated we've once created. Everything works correctly so far. I guess the reassigning did lots of good.
But is it correct that all GeoFence related and newly introduced workflows/actions are disabled by design? This would make sense to me since on the first look those workflows are not really needed in every use case. I could deliver a list of those if needed.
What boggles me though is: How could I check which one managed Solution did a failed DeleteAndPromote system operation try to remove and do you guys think this could be an issue somewhen? So far only this failure. We'll do more testing now but it looks very good so far.
After each upgrade, the Field Service upgrade package automatically triggers a Solution Health Hub run for the Field Service ruleset. Consider reviewing the results which will highlight a number of potential issues, including inactive processes.
Beyond upgrades, running the Field Service health rules and reviewing the results on a regular basis is just good practice to easily mitigate common issues and keep your system in healthy standing.
Business Applications communities