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
I have tried several time to create a Task on my tablet and have filled in all of the fields necessary but the "Save" and "Edit" remains grayed out and the only option is to "Close." When I close it, it doesn't save it and I am back to step 1. Any ideas why it wouldn't save? The Task Entity is set up to allow CRM tablet and mobile use.
I've never come across this before where all fields are filled in and you can't save it. I went into CLOSED TASKS on-premise and it isn't there either. So, nothing is saving. ANY ideas?
Hi, I seem to have this same issue in the Interactive Service Hub.
Did you ever manage to solve your issue? Maybe this solution works for me too..
I was having this problem on mobile (never tried tablet) and the issue ended up being a required field 'Status Reason'. I set it to optional and that worked for me.
Thanks InssuranceCRM. I've managed to solve it.
Strange thing is, in our environment the Status Reason was not required but optional. But I noticed some business rule on the Task entity that made the status required. It looked like some test rule somebody made and forgot to deactivate/delete.
As I am the only person that modifies the system, could it be someone at MS who messed this up? :)
Business Applications communities