• RSO: Inefficient resource utilization, Excessive idle time for technicians

    To address white space reduction, we implemented customizations to improve scheduling efficiency. When a booking was finished early or started late, we updated the planned completion date and time dynamically. This adjustment ensured that bookings on the schedule board reflected real-time availability, providing better clarity.

    Additionally, this approach made the resource's available time accessible for the next run of the intra-day RSO, optimizing resource utilization. To achieve this functionality, we utilized Power Automate along with custom plugins, enabling seamless updates and improved operational efficiency.

  • How to handle the Non-productive activities( Internal Meetings, Boot Camps, Workshops)

    Resource have their daily standup and planned meetings and similarly other unplanned activities. In that case, RSO is not scheduling resources for the non-working time. so that’s why its reflecting as white space over the schedule board and its not showing the clear visibility to dispatcher. So, for the non-productive activities, we are creating NPA activities and marking as scheduled but do not move so the RSO can move the scheduled activities.


    These actions significantly reduced manual intervention, streamlined operations, and enhanced the overall efficiency of the RSO system.

  • Handling Complex Expressions with Roll-up Query UI

    Handling complex expressions can be challenging, especially since there is no out-of-the-box (OOB) UI available to manage them effectively. For scenarios where complex expressions need to be implemented and might require frequent changes, I recommend using the Roll-up Query UI.

    Why use Roll-up Query?

    • Configuration Made Simple: The Roll-up Query UI allows you to configure complex expressions without custom coding or Power Automate.
    • Fetch XML Saved in Dataverse: Microsoft stores the Fetch XML for each expression directly in Dataverse. This means you don’t have to create your own Fetch XML manually.
    • Dynamic Data Validation: You can use the saved Fetch XML, pass IDs dynamically, and validate your data efficiently.

    This is a highly effective solution compared to hardcoding conditions in your code or Power Automate. It simplifies the process and improves maintainability.

    Let me know if you need further details or assistance with implementation.

    Thanks!