Fahmeeda Yaseen Dynamics CE & Power Platform Solution Architect

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.

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 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!

Problem:

• Only one order orchestration flow can be active at a time.
• You cannot configure multiple orchestration flows for the same order type or business event.
• This forces all validations and logic into one complex orchestration, making it hard to maintain and extend.

Proposed solution:

1. Allow users to create and activate multiple order orchestration flows and let them run in parallel.
2. Each orchestration can handle specific business events or logic independently, instead of putting everything into one flow.
3. This makes complex orchestration easier to manage, extend, and maintain in the future.

Currently, when an incoming call is received from an existing customer, the system only displays the phone number in the active conversation pop-up.

The customer record associated with that phone number is not automatically linked or populated.

The expected behavior is that the system should automatically identify the customer based on the incoming phone number and display the corresponding customer information in the conversation pop-up.

This should be a default feature, as it is a core requirement for efficient contact center operations.

Problem Statement:

Dynamics 365 CE lacks native support for dependent picklists, multi-select dependencies, and active/inactive option management. Organizations with complex business scenarios face challenges with scalability, maintainability, and performance when using JavaScript-based filtering for Option Sets. This limits flexibility, increases technical debt, and complicates configuration.

Proposed Idea:

This idea proposes a lookup-based framework using Dataverse tables and N:N relationships to enable configurable parent-child picklists, multi-level dependencies, and lifecycle management. The solution minimizes JavaScript, scales to hundreds of values, preserves historical data, and allows business users to manage picklists without deployments, improving usability, performance, and maintainability.