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 2 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
We are having one OOB description field in the knowledge article entity which is of KbEditorControl.
We want to make that field read-only based on some conditions but, none of them are working.
Please suggest a way to make that field as read only.
You can use Business rules on the Knowledge article entity to lock/unlock a field. I have used a simple condition like if the "created by" has data then lock the description field. You can use similar logic and create business rules to lock the field.
Thanks and regards,
Thanks for your reply.
The business rule as well is not locking the field in the form.
the field is of type KBEditorControl (OOB richtext field).
If the field is OOB Description field then the business rule will work. Kindly provide the schema name of the field you are referring to.
The schema name is content
Business Applications communities