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
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 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
For some reason, the From field is disabled for me on the email creation screen in workflows. This is on disabled and even brand new workflows. The field isn't read-only on any entity forms. My account is a System Administrator. Does anyone know what might cause this?
This is on CRM 2016 SP1 on-premise (v. 8.1.0359).
This field are disabled at the main form?
No, the main Email form works fine, no disabled fields. It's only disabled in workflows.
EDIT: The From field is disabled/read-only on the main form. Not sure what I was looking at the first time.
It is in one of my client systems as well. Have you figured out why this is the case?
It appears to be an issue with 2016 update 1. This page offers a solution, but I haven't tried it: http://stackoverflow.com/questions/38802564/from-field-locked-on-email-form-in-dynamic-crm-2016
4. Save changes, zip back the Solution folder and import it back to your CRM organization.
This did resolve my issue. I'm not entirely sure that it is an issue with just 2016 Update 1 - looks like it is related to different DB versions. I have several clients on 2016 Update 1, but only one client had this issue. The DB version that had this issue was 184.108.40.2062.
Also, just to make double sure the lookuptypes suggested in this answer were correct, I exported the from field from another system. They are correct.
Thanks for the quick reply!
Business Applications communities