Published on September 13, 2017
1. Why .NETdevelopers struggle with CRM Development?
2. Things a CRM Developer should keep in mind... They have to learn the mysterious ways of CRM development they need to learn the the quirks and the way things work with Microsoft Dynamics CRM development. CRM is unpredictable and sometimes very difficult to persuade it to do as you would like This makes experience very important because to learn how things work, you have to go through the process of things not working (often in many different flavours of not working) before it works There are some shortcuts but often you have to go through the painful process yourself.
3. There are some shortcuts but often you have to go through the painful process yourself.
4. Plugins When a CRM developer starts developing a plugin, he will learn the all the steps you need to take and the hoops you need to jump through...below is a quick go through of process: ● setup up CRM Developer toolkit ● User has to be CRM Admin ● Isolation mode? if none user has to be a deployment administrator ● plugin needs to be signed ● crmRegister file needs to be checked out ● These are the simple things you need to do to create and register a plugin, that’s without even thinking about the code and if it works, testing, debugging etc.
5. CRM Tools ● There are lots of tools where you have to put the server, the CRM Discovery URL, the OganisationService url. ● At first you guess what they are, fail a bunch of times until you knuckle down and find out where those urls are, what they do and why the tool needs them. ● Use Microsoft Dynamics CRM services in code ● Then one day you find they are hidden in CRM under settings, developer resources! ● CRM 2011 – Discovery and organization service are held in settings
6. WHY .NET/C# struggle developing ● Sometimes companies don’t want to pay for CRM developer or have C# resources which they think they will use to do some CRM plugin customization. ● This theory seems like a sound idea, the actual C# code in a plugin is usually quite small and not overly complex but for a C# Developer with no CRM experience it’s a total nightmare ● C# developers with no Microsoft Dynamics CRM development experience don’t understand how data in the CRM website is structured in SQL Server database How CRM works with customizations The different types of customizations to choose from, without this knowledge how do you pick the correct customization type. How do I create a plugin How do you register a plugin – common plugin errors How do I write a query to retrieve related records in CRM ● Whilst the C# developer goes through learning how things don’t work, it takes the developer a lot longer to write the plugin (if they manage it)
7. Hands on experience is vital ● During the minor setbacks the CRM developers will read blogs, the SDK and work out why it doesn’t work. ● The CRM developer will end up with a working customization, e.g. plugin but will also have a better understanding of creating CRM customizations and a more in depth knowledge of how the CRM customization works.. ● Creating the customization gives you a deeper knowledge of CRM development because reading about CRM development won’t tell you about what doesn’t work. ● If you think about knowledge as 3 dimensional object, reading about CRM Development gives you one view of the object. Getting it working and overcoming the errors during this process gives you a different view of the object.
9. Summary ● Experienced CRM developers make less errors because they have learnt to stop making these errors through experience and bug fixing those problems. ● Due to the experience and knowledge gained through experience and reading they will make better choices about what customization work well in certain scenarios ● One the key roles experience developers have is advising and peer reviewing less experienced developers. Finding problems and bugs earlier in the process can save you hours if those same bugs are found when the CRM customization has gone to the customer.