Monday, December 8, 2025

SLA doesn't retrigger when the the criteria changes

Behavior:
Once SLA criteria is met, it reaches terminal status and no change to the status happens even if the criteria changes, resulting in newly applicable success conditions not met.

Steps to retrigger SLA when criteria Change:
From the Copilot Admin center App, Enable SLA Recalculate option.

Enabling SLA Recalculate ensures that:
  • The SLA is recalculated whenever the criteria change.
  • A new SLA instance is created, even if the previous SLA condition was already met and its success action executed.
  • This allows subsequent success actions tied to new criteria to run without manual intervention.

SLA is not triggering after solution import

Issue: SLA is not triggering after solution import 

Resolution: The SLAs remain inactive post import, hence
1.Manually activate and set as Default post every import

2. Exclude the SLAs from the solution after the first import, that will avoid this additional step.


Sunday, December 7, 2025

Field mapping is not working on Field Service mobile Online

Issue: This is a known limitation on Field Service Mobile online that the field mappings do not work.

Resolution:
Custom logic is needed to populate the fields.

-Ensure the tables being mapped are enabled for Mobile offline
-And Use Xrm.Webapi.offline.RetrieveRecord to retrieve the record and populate it

Email template

Issue: The image pasted within an Email template - when moved to another organization - through solution blurs

Resolution : Add the images into a publicly accessible website and refer using href in the Email template

What will not work:
1. Adding it in a webresource - This wont render in the email, As this will need access to CRM.

2. Adding it on Power Pages - as a webtemplate - AS this will still need to go through security gates

Wednesday, February 26, 2025

Principles for Discovery and Design in Dynamics 365 System Implementation

When undertaking a Dynamics 365 implementation, whether it's for a new system or transitioning from an old system, the discovery and design sessions are pivotal. Here are principles for successful discovery and design sessions in any Dynamics 365 project:

1. Deep Business Process Analysis:

   - Conduct in-depth reviews of the client's business processes, employing advanced process mapping techniques to gain a holistic understanding of the operational landscape.

   - Utilize interactive workshops to extract nuanced insights and pinpoint opportunities for streamlining with Dynamics 365.

2. Maximization of Native Capabilities:

   - Prioritize the adoption of Dynamics 365's inherent features, promoting a configuration-first mindset.

   - Reserve custom development for scenarios where native solutions cannot fulfil critical business requirements.

3. Comprehensive Stakeholder Engagement:

   - Implement a structured engagement framework to ensure comprehensive input from a diverse group of stakeholders, fostering a sense of ownership and collaboration in every key decision-making process.

4. Objective-Driven Implementation Strategy:

   - Establish a set of well-defined, measurable goals for each phase of the project, that align with the strategic vision of the organization and the capabilities of Dynamics 365.

5. Adherence to Success by Design Principles:

   - Integrate Microsoft's Success by Design methodology to guide the implementation, leveraging its structured approach and industry insights. More details here: Success-by-Design

6. User-Centric Story Crafting:

   - Develop intricate user narratives that encapsulate the diverse interactions with Dynamics 365, focusing on intuitive user experiences and functional completeness.

7. Iterative Prototyping and Feedback Loops:

   - Employ a rapid prototyping model to construct and refine system designs, utilizing stakeholder feedback to iterate towards an optimal solution.

8. Rigorous Documentation Practice:

   - Maintain meticulous records of all requirements, decisions, and design iterations to serve as a comprehensive knowledge base for the project lifecycle.

Migration Strategy for Transitioning to Dynamics 365:

9. In-Depth Legacy System Evaluation:

   - Perform a detailed analysis of the legacy system, capturing its structure, data intricacies, and interdependencies to inform the migration strategy.

10. Strategic Migration Roadmap Development:

   - Craft a migration blueprint that delineates the migration's objectives, scope, and methodology, complemented by a phased timeline and critical checkpoints.

11. Data Mapping and Transformation:

   - Execute a thorough data mapping exercise to transition data to the new Dynamics 365 environment, ensuring data integrity through meticulous cleansing and transformation processes.