Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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
I have an issue with work order starting number setting located in field service -> administration -> field service settings.
The problem is I once wrote down a big number in this field and successfully generated a work order with that number. Later on I decided to delete this work order and generate work orders starting from another number which is much smaller, and I'm constantly getting this error.
The work order with number 300002 is deleted but somehow it doesn't matter.
Try adding a prefix to your new number?
I know someone else had the same issue as you but didnt provide a solution. You may have to contact Microsoft and see how to reset the number
have you tried to remove any value from field service -> administration -> field service Settings -> Work Order Starting Number, then create a new work worker.
Then reenter your new starting number again and try create a new work order again?
Yes, I tried that and the new work order has that big number 300002, although work order starting number field is empty.
I tried to add prefix to reset the numbering but it made no difference.
This shouldn't happen at all and looks like the setting is cached somewhere or not invalidated.
That's why I recommend you to raise a support ticket with Microsoft.
Business Applications communities