Breaking news from around the world
Get the Bing + MSN extension
The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
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 | View 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 | Talent TechTalks | Upcoming TechTalks
We encountered an error when editing permissions for a field security profile on a newly configured field,
However, when trying the same thing on other fields that were already enabled for field security, the changes were applied without any issues.
To uncover the cause for this error, we needed to trace back to how the original settings for field security were configured.
If the field had not been previously enabled for field security, we would have had to enable this in the classic solution explorer:
Whether or not you receive the error after editing field permissions is determined by what steps you take next.
If you press Save without publishing, the field that you have just enabled for field security will appear in the list of fields available for field permission editing for any field security profile.
The reason for the original error was caused by trying to make field permission changes prior to publishing the enabled field security. Once we published customizations, we were able to edit field permissions to the field in question without error.
Despite the newly configured field appearing in the list of fields available for field permission editing in a field security profile, avoid making edits without first publishing!
Business Applications communities