Skip to content

Expert view: Interviewing a developer with over 10 years of experience in MS Dynamics.

Interviewing a developer with over 10 years of experience in MS Dynamics.

Welcome to Solution for Guru, where we delve into the minds of industry leaders and experts. Today, we have the privilege of sitting down with Serhiy Slusarchuk, a distinguished Customer Relationship Management (CRM) professional focusing on Microsoft Dynamics CRM.

Serhiy Slusarchuk is a seasoned expert whose journey in the tech industry has been marked by his profound understanding of CRM systems and a keen eye for leveraging Microsoft Dynamics to enhance business processes. With an extensive background in implementing and optimizing CRM solutions, Serhiy has become a trusted authority in helping organizations streamline customer interactions and drive meaningful outcomes.

As we navigate the intricacies of Microsoft Dynamics CRM, we'll gain insights into Serhiy's experiences, strategies, and the evolving landscape of CRM in today's dynamic business environment. Whether you're a seasoned professional in CRM or someone looking to grasp the fundamentals, this interview promises to be an enlightening exploration into the world of MS Dynamics CRM with Serhiy Slusarchuk as our guide.

Join us in unraveling the expertise and wisdom that Serhiy brings to the table as we uncover the nuances of CRM excellence in the age of Microsoft Dynamics:

You work in the energy sector, don't you?

  • Yes, I work in an energy supply company as a programmer.

When did you start working with MS Dynamics?

  • My first introduction to MS Dynamics took place in late 2013.

Why did you choose MS Dynamics, and what alternatives were you considering?

  • I really liked the architecture of the software product, the vast possibility of development, its meticulously designed functionality, the unlimited possibility of its extension, and its integration with other Microsoft products. It’s clear and logical.

The only alternative at that time could be SAP ERP. However, we opted for MS Dynamics because it is more tailored to the needs of the company and was adapted 

for enterprise accounting needs, which significantly reduced in the future the number of customizations, additional improvements, etc.

Why did you decide to become an MS Dynamics developer?

  • This happened by chance. I got a job as an engineer in the company's IT department. After 2 years of work, I heard it is planned to implement the Microsoft Dynamics AX ERP system. I was very excited about this and asked for a transfer to the development department, which was being formed for implementation at that time. I was accepted because I am a programmer by profession. A difficult period of implementation began. It was challenging yet rewarding; everything was exciting and new, and I gained much new knowledge and mastered my programming skills. I rather enjoy working with this product

While working with this platform, what difficulties did you face in the development process?

  • Of course, there were complex and very time-consuming tasks. Still, in 99 percent of cases, they were "problematic" due to the tight deadlines, the fuzziness of technical tasks, and insufficient technical knowledge. For implementing some complex tasks, it was necessary to gain some knowledge first and do it very quickly.

What advantages and disadvantages of this platform can you highlight based on your experience?

  • For many years of work with the product, I did not notice any shortcomings, except that there was slight slowness of the system, and even that was due to the physical limitations of the hardware on which the system was installed. Regarding pros - extraordinary thoughtfulness, unlimited resources for further upgrades, development and functionality extension, close communication between modules, clarity for the user, an unusually large range of development tools, the ability to work with a large amount of data, the simultaneous work of a large number of users.

Can I buy modules of MS Dynamics separately?

  • You can order the refinement of the existing functionality or the development of a brand new module from the development companies for the specifics of the enterprise itself. If the company has its own staff of programmers, then the completion of new modules occurs independently.

What is nice about modules is that you can hide them from the end users to not distract them.

What database do you use?

  • Database deployed to SQL server

Describe your usual MS Dynamics development workflow.

  1. Exploring user needs, discussion (input parameters, expected result, etc.);

  2. Brainstorming the ways how to solve the problem;

  3. Development. If it is the development of the report - preparation of the template, and
    way of data output according to the desired format;

  4. Analysis of tables and relations from where you want to display information;

  5. Writing a class that will handle input parameters, process SQL queries, output data, and additional information. While expanding the existing functionality, I create new tables and corresponding forms for them and classes that will handle processes according to technical specifications. If necessary, data is imported/exported;

  6. Presentation of development results to users. Product testing and getting feedback.

  7. Bug fixing and improvements if additional requests were provided;

  8. Production deployment, granting access to end users.

What additional stack of technologies and software do you use in your work?

  • Additional development environments, such as Visual Studio, Notepad++, Toad for SQL server, etc., are used.

How many active users are currently in your MS Dynamics?

  • By far, the system has about 6000 users, with 200-250 users being active on a daily basis.

What qualities should a developer have for the MS Dynamics platform?

  • Analytical skills, since in most cases, the developer himself must understand from which tables and how to display data, think over the mechanism and architecture of the future functionality, and leave "space" for future expansion of the functionality, even if it happens a few years after writing the revision;
  • Multitasking is essential. Leave one task and work out another, which is more pressing than working over the same task.
  • Ingenuity. This is all about solving issues when the solution seems extremely difficult or dubious;
  • Steadiness. Solving many problems requires hours of analysis and concentration. Since the system is modular and these modules are closely related, you need to be very careful in any operations not to damage the mechanisms or data in the "neighboring" modules created earlier.
  • Technical skills. Product development requires deep technical knowledge in diverse areas - programming, databases, applications, etc.
  • Sociability. The more communicative the developer, the easier it is for him to communicate with users, get clearer technical tasks, communicate with managers of a higher level and the directorate;

Do you plan to continue working with MS Dynamics, and what do you see as the future of this platform?

  • Absolutely! I didn’t even plan to change my direction as a Microsoft Dynamics AX (or subsidiaries) developer 
  •  This is a very promising platform, and it will exist for a very long time and gain distribution worldwide in every company, even minor.