of the
When creating new entity, follow step-by-step instructions and you’ll be fine. Except if you want to enable the entity for Knowledge Management later on, you’ll find the relevant checkbox disabled. What the?
To work around this behavior (that looks suspiciously like a bug), open Settings > Service Management > Embedded Knowledge Search, check the box for your entity in Record Types list and save the changes.
Follow the same process to disable Knowledge Management for your entity. Note: when Knowledge Management is disabled, N:N relationships between the entity, Knowledge Articles (shiny new KBs since CRM 2016) and Knowledge Base Records (Parature integration) are not removed which makes life much simpler if you have data or added the KB sub-grid to the entity form. Nuke the relationships manually or keep them around in case your want to resurrect Knowledge Management later on.
Thanks George! You just saved the day!
Thank you soo much. After hours of research
just once in this world I would like to see a technology that includes a list of the errors that occur. I go to the Settings//Service Management/Knowledge Base Management and click on Embedded Knowledge Search and I get a error. an error that gives very little information as to why or what went wrong. Thanks for nothing Microsoft.
rant complete.
I know this is an old post but I was happy to find it! I created a new BPF to the Knowledge Article entity and the new BPF table has ‘Allow Knowledge Management’ disabled. What do I gain by enabling it? I am having a problem with my BPF not Publishing articles like it does when using the out of the box ‘New Process’ BPF. Does anyone have suggestions?
From memory it adds ability to relate your custom table to KB articles via N:N relationship.