589
We are implementing Dynamics 365 on premises for a customer, I'm confused a little on which to choose between knowledge base or knowledge article? Any insights on how the future of knowledge base and knowledge article? whats the advantage of each?
*This post is locked for comments
If you are starting a new implementation, I see no reason to use the old entity, as it will probably be deprecated at some point in the future, and I don't see any significant benefits over the new entity.
If you have an existing implementation with the old entity, then the decision is not so easy. If some of the new features (e.g. versioning or translation) are useful, then I'd move to the new entity, but if you're happy with the functionality of the old entity there's not a compelling reason to migrate
Hi NITHYA,
Thanks for the response, however i understand the difference between both and how and where it is used. But what i really want to know is why to use new entity when old one is sill working and will not be deprecated. I want to know the future of the old entity so that we can plan which entity to use etc.
Hi Hari Narayanan,
Refer the community thread below.
community.dynamics.com/.../233048
Hope this helps.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (