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 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
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
OnPrem Dynamics CRM 2015
We are finding that certain fields in some browsers are locked (Read Only, which they should be) in Chrome or Firefox but in IE the field is unlocked for the same user across these browsers..
I've yet to find any resources surrounding this and thought I would engage with the community.
This is happening in multiple environments which we run and not all are distributed, some are standalone)
Appreciate any insight.
Sorry if this was confusing. So these are standard fields with no special code running to set this. These are basic fields with either the field attribute set to read only or field level security set on the field. When you hop from one browser to another the field the security is no longer in place (visual lock indicator missing) and in some instances even though the field appears to be unlocked or the field level security is gone, you still are unable to edit the field.
Hope this helps. :)
There is a recent update released for CRM 2015, possibly it is a bug if you can reproduce it without any code./ customization.
Worth checking if this could be related to this.
Reading through the list of fixes, nothing there seems to apply.
But thank you.
Business Applications communities