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 2 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
After Update from v 9.2 to 11.2
that messages shown
1) have you enabled resources access to the FS Mobile APp on the Bookable Resource Form / Record?
2) Which version of the mobile project are you using?
3) can you also send a picture of your settings page in teh Mobile app?
1- I dont understand what you mean !
2- i use version (woodford_12_0_0_43085) version of the mobile project and Project templeat (FSDyn365_1.0.1322 )
3-winch settings page need ?
i followed that link exactly
On the Bookable Resource record in Dynamics, there is a field called Enabled for Field Service Mobile. Is that field set to Yes?
Which version of Field Service is your organization using?
Settings in FS Mobile:
On the Bookable Resource record in Dynamics:
version of Field Service in my organization using
Did you publish your Woodford project with a target version of 11.2? Did you associate the project with a security role that is also associated to your mobile user?
Yes i published wood ford project and set security role fro users
the problem is solved but the issue in my permission on Active Directory on Azure
Business Applications communities