Working on the RCRMT project was an important milestone because it involved Microsoft Dynamics 365 (MSDYN365) for the first time. The project came with its own set of challenges, valuable learnings, and opportunities for growth. Here’s a look at the key experiences and lessons from this journey.

 1. Understanding MS Dynamics 365 for the First Time

It is the first exposure to MS Dynamics 365. The biggest challenge was the steep learning curve—understanding the platform’s structure, libraries, components, and overall flow within a short time.
Despite the initial difficulty, diving deep into MSDYN365 helped build strong foundational knowledge of the framework.

2. Issue With Custom Header Implementation

One major requirement of the project was to implement a custom navigation header.
However, the custom header interfered with the platform’s built-in cart component.
Because the custom header was not sending the required information to the cart, several features started malfunctioning. This created a mismatch in the expected system flow and caused critical issues.

3. Solution: Switching Back to MSDYN365’s Built-In Header

After analyzing the issue in depth, it became clear that the custom header was the root cause of the failure.
The remedy was to use MSDYN365’s default header, which is fully compatible with the cart and other components.

Once we switched back:

• The cart began working smoothly
  
• The system regained stability
  
• All components followed the correct functional flow
  

This solution reinforced the importance of respecting framework-level dependencies.

4. Lessons Learned

This project highlighted a valuable principle.

Functionality and integration must come before customization. Before building custom components, it’s crucial to understand the platform’s built-in features, their relationships, and how they handle data and communication.

This experience taught us:

• Analyze framework capabilities thoroughly
  
• Avoid unnecessary customizations when built-in components are already optimized
  
• Prioritize system stability and compatibility
  

5. Professional Growth

Despite the challenges, the project greatly enhanced skills:

• Improved understanding of MSDYN365
  
• Stronger problem-solving abilities
  
• Hands-on experience working within a complex enterprise framework
  
• Increased confidence for future projects with similar architectures
  

This experience laid a strong foundation for tackling more advanced projects and making better architectural decisions.

Conclusion:

The RCRMT project was more than just a technical task—it was a learning journey.
It taught  how to approach enterprise platforms thoughtfully, balance customizations with built-in capabilities, and solve problems efficiently.
Every challenge turns into an opportunity for growth, and these learnings will guide future implementations in a more structured and confident way.