Salesforce Professional aiming to use his Salesforce background to add a new CRM tool (dynamics 365) under his belt.
It’s a very user friendly system to learn and navigate. If you have used other CRM solutions this will be easy to master in a short term
Thank you Sameer
They are very similar in platforms and user friendly and mostly guided. My answer will be yes it should be easy to master.
Thank your Khalid
Define “master” to begin with. Are you talking from a developer perspective? Sysadmin? Functional? There are obviously differences in the learning/change curves for each of those.
Actually, I am a Salesforce Admin & Developer at the same time, I’ve got certifications and hands-on experience on some challenging projects. but if I can choose between the two I can say, Developer.
Thank you Lorne for your Answer.
YES, If the consultant is a user with experience in the use of programs such as excel or word
As you have development experience in MS-centric languages you should be able to make the transition. I still wouldn’t classify it as “easy”, but certainly easIER than if you were, say, 95% Java experienced. A few things to keep in mind with D365:
- There are still multiple “admin” portals and experiences that you need to figure out to be able to work with the platform. Perhaps someday MS will boil it down to “one portal to rule them all”, but that day is NOT today ;)
- To be most effective you need to start your learning with the CDS, then Power Platform (as D365 is increasingly just a collection of complex PowerApps stitched together with some other stuff), then the remainder of the “above the water” portion
- There is one major gotcha you won’t see documented ANYWHERE (but I have it on good authority the product group is aware of and trying to figure out a way to dig out of this hole they created); when you import any solution into a tenant environment, be it directly from MS or ISV or pure custom, it gets applied ON TOP OF what is there when you import it. Think along the lines of 90’s-era procedural code. And like procedural, if you then apply something else on top of what you added previously the ONLY way to remove the layer you had added previously is to first remove the most recent layer(s). And removing things in D365 is almost with zero exception, PAINFUL. Why? Because the majority of what you will add in will need to reference at least one, and quite often many, of the core entities like Lead, Contact, Account, Product, Opportunity, etc. And in the UCI these cross references have to be undone at multiple levels in order to remove anything. I have had MS support trying to figure out how to remove the MS-created Marketing App (the newer one that provides marketing automation not the legacy piece of crap) for SIX MONTHS. Yeah, you read that correctly. MS can’t figure out how to successfully remove their own software from their other own software.
This will mark this comment as best reply and close your question.
Are you sure?
This will close your question without a Best reply.
Are you sure?
This will report this content as inappropiate to the moderators.
Are you sure?