Vikas Gupta

It was an integration-based project: an integration between a .NET application and a Dynamics CRM. We customized the CRM to work parallelly with a .NET sales application and used web services to smoothly integrate the systems in real time.

The client was one of the government organizations in Bahrain and the project's goal was to move Dynamics CRM 2016 (on-premise) to Dynamics CRM 365 (on-cloud).

Project Steps:
1. Moved all the customization in the solution to the cloud.
2. Migrated the data using an Excel sheet upload.
3. Created all business units and users' relevant security roles.

The project consisted of a CRM implementation.

Project Steps:
1. Gathered functional requirements.
2. Implemented functional gap/customizations.
3. Filled the gaps using workflows, JavaScript, form customization. and custom plugins.

We built a web application for an investment banking client. It was used internally for fetching data from different data sources and then process emails for different investors.

Project Details:
• For the end user's app, we authenticated with AD.
• The app fetched data from SQL, files from a shared drive, and processed the email based on specific criteria.

I developed a Web API for a real estate client to integrate their sales system with the Dynamics CRM.

Project Details:
• The sales system was a C# Windows-based application that we had to install on each client machine.
• We chose Dynamics as our on-premise web-based solution.
• The Web API locally hosted a service to integrate two systems.
• It was a near real-time integration.

This was a short-term and quick project where we installed and configured NAV and Business Central on premise; I was involved as a technical consultant.

Project Details:
1. Set up Business Central.
2. Installed and configured the development environment.

I worked on a DevExpress tool to develop a Windows app for our marine services client.

Project Details:
• Our marine client discontinued their ERP system.
• For their work, they required a small utility app.
• We used the DevExpress framework to build the app.

Project Requirements
The sales team chase after hundreds of various leads in a day and sometimes they need to convert multiple leads into lost opportunities at once.

Solution
I developed a custom workflow where a user can select a group of opportunities/leads and indicate that they would like to flag it as "lost" via the flag. Then I manually trigger the workflow and custom workflow will convert all those specific flagged opportunities to the lost category.

I can share the code if you would like more details about how I achieved this.

Project Requirements
Users are required to obtain approval whenever an opportunity moves from one stage to another; this applies to both progression and regression.

Solution
I developed a solution that involved multiple CRM standard and custom workflows, custom fields in the opportunity form, and also a required custom entity.

Details:
I placed all required fields on the opportunity page. Once a user chooses the next stage, the system will select the approver team. Then based on that, the system will trigger the workflow and create a record (a custom entity) for the approver. A crucial part of the system is that until approval is given, no one can move onto the next stage. However, once approval is received, the record moves onto the desired stage. The same process applies to all stages regardless of whether it's progression or regression.