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
FieldOne Sky, the MS CRM field solution, comes up with a free Windows app that you can use as an emulator/tester for the mobile functionality. In my opinion and after reading other users’ experiences on the web, the app is still getting mature and you *may* encounter a crash.
When it crashes, the app simply vanishes from the console without any warning or error log file.
How do you know what caused the error, so that you have at least an opportunity to DIY a fix
So what do you?
After following some traces and doing random searches in the temporary files, I did hit upon the error log which is contains the actual error that caused the crash.
The mobile app maintains the error log in a file called crash.log (what an appropriate name )
The file is present here: C:\Users\<loggedinUser>\AppData\Local\Packages\FieldOneSystemsLLC.FieldOneSkyMobile_xxxxxxx\LocalState\MobileCRM
Another important files that keep the execution log can be found here
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FieldOneSystemsL_<a big guid>\Report.wer (open this with notepad)
Happy diagnosing !!
Business Applications communities