When you need to innovate, you need collaboration. Marissa Mayer
Ekhor is an experienced Microsoft developer with experience in DevOps processes for Dynamics 365
Zoe: I think people might find it scary to throw money at something they can’t see. With bespoke solutions, realistically you could get anything; you hope you’ll get what you asked for, and something similar to any proof of concepts you’ve seen, but I think there’s always a fear that clients will end up with something a bit different to what they wanted, even if it technically ticks all the boxes. With Dynamics 365, you can only stray so far from what comes out of the box; the method of navigation is always going to be similar, the forms will always look similar and the look and feel of the solution in general won’t be all that different from any other Dynamics 365 instance. To me it seems like this very big, expensive safety net, that means developers can’t run too far from what the client is expecting. I also think this can be a very bad thing; it seems as though some clients are so excited to already have this application before development really starts that they pick Dynamics 365, when in reality they want something completely different, but don’t want to wait to see what .NET developers can give them. This results in a Frankenstein creation that is trying really hard to not be Dynamics 365, and results in neither the client nor the developers being happy with it.
Ekhor: Do you think there are enough opportunities for a .NET software engineer within the Dynamics 365 space?
Zoe: In every project I have been on, even with them all having a customisation-first approach, plugins and C# development have always been required. I think as Dynamics 365 evolves and is updated with new features, a few things that are done as standard in plugins will no longer need code; but from my experiences in the Dynamics 365 space I think there will always be something for a .NET software engineer on Dynamics projects, even if not necessarily a reliable amount of work.
Ekhor: Without going into client specifics, what types of solutions have you worked using the Dynamics 365 platform?
Zoe: Most of my work has been either CRM 4 or CRM 2011 upgrade projects, requiring migration to the latest version of CRM, whatever that is at the time. I have also worked on some upgrade projects where complete redevelopment was required, due to all of the changes from CRM 4 to Dynamics 365. Although the upgrades have been simpler from the point of view of meeting client requirements — it should just do everything the old system did — I have found the new development projects far easier in terms of implementing the functionality as it is meant to be in the latest version. The issue with upgrade projects is what may have been a perfectly good idea in 2007 when developing a CRM 4.0 solution, does not necessarily translate into a good idea in 2019, when migrating to Dynamics 365.
Ekhor: Which areas in the industry are you currently focusing on?
Read previous Developer viewpoints