Skip to main content
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Service | Customer Service, Contact Center, Fie... / RSO - don't schedule J...
Service | Customer Service, Contact Center, Fie...
Suggested answer

RSO - don't schedule John and Jane together, ever!

(0) ShareShare
ReportReport
Posted on by Community member
Hello, 
 
Is there an elegant way to prevent John and Jane being scheduled together simply because they despise one another using RSO. 
 
Thank you, 
  • Statsoni Profile Picture
    Statsoni 2 on at
    RSO - don't schedule John and Jane together, ever!
    It sounds like you're looking for a way to prevent John and Jane from being scheduled together using RSO (Resource Scheduling Optimization), which is often used in the context of workforce scheduling or resource allocation. While I don't have the specific details of your system, I can provide a general approach that you might consider:
    Define Constraints:
    Determine the constraints that need to be satisfied. In this case, the constraint is to prevent John and Jane from being scheduled together.
    Data Representation:
    Ensure you have a data structure that represents the schedule and includes information about the assigned resources and tasks.
    Algorithmic Approach:
    Implement an algorithm that takes into account the defined constraints. This algorithm could be part of your scheduling logic. Here's a simplified example:
    def schedule_task(task, current_schedule):
        available_resources = get_available_resources(task, current_schedule)
        eligible_resources = filter_unrestricted_resources(available_resources)
        eligible_resources = filter_disliked_resources(eligible_resources, task)
        # Use a scheduling algorithm (e.g., RSO) to choose from eligible_resources
        # Assign the chosen resource to the task in the schedule
        return updated_schedule

    Filtering Mechanism:
    In the filter_disliked_resources function, you'll need to filter out resources that are disliked by the task. In your case, it means filtering out John if the task dislikes him.
    Integration with RSO:
    If you're using an existing RSO framework, you'll need to integrate your constraint logic within it. This might involve overriding certain methods or integrating your constraint-checking logic into the scheduling process.
    Testing and Optimization:
    Test your scheduling logic thoroughly to ensure it's working as expected. You might need to adjust and optimize your algorithm based on real-world usage and feedback.
    Keep in mind that implementing specific constraints like avoiding scheduling certain individuals together can become quite complex, especially within an optimization framework like RSO. The key is to integrate your constraint logic seamlessly into the existing scheduling process. Myjdfaccount
    Remember, the exact implementation will depend on your system architecture, the tools you're using, and the constraints you're dealing with. If you have access to documentation or support for your RSO framework, they might have specific guidelines for implementing custom constraints like this one.
  • Suggested answer
    RudyZhang Profile Picture
    RudyZhang Microsoft Employee on at
    RSO - don't schedule John and Jane together, ever!
    Hi,
     
    Your attempt to prevent User A from scheduling with User B via RSO is not supported.
     
    Our team has proposed the following alternatives.
     
    Option 1: You can try assigning different skill labels to User A and User B. This may reduce the likelihood that they will be scheduled together because RSO will consider the requirements of the job and the unique attributes of the resource when scheduling the job. However, this may not completely prevent them from being scheduled together because RSO considers many factors when making scheduling decisions.
     
    You can learn specific details about the characteristics of a given resource through the documentation at the following link
    Specify characteristics for resources - Dynamics 365 Field Service | Microsoft Learn
     
    Option 2: In Dynamics 365 Field Service, you can manually schedule work orders using the Schedule Board or the Schedule Assistant. These tools allow These tools allow dispatchers to schedule a single job at a time and can provide more control over the scheduling process. These tools allow dispatchers to schedule a single job at a time and can provide more control over the scheduling process.
     
    You can learn how to manually assign work orders by following the link below
    Schedule a work order - Dynamics 365 Field Service | Microsoft Learn
     
    The two alternatives mentioned above have their own drawbacks, so if you think this feature is essential, you can use the following link to make your suggestion to Microsoft.
    https://experience.dynamics.com/ideas/
     
     
     
    I hope my answer is helpful to you! If you have any other questions, please feel free to contact me.
     
    Best Regards,
    Rudy Zhang

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Now Available: 2025 Release Wave 2

Quick Links

Ramesh Kumar – Community Spotlight

We are honored to recognize Ramesh Kumar as our July 2025 Community…

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

#1
Muhammad Shahzad Shafique Profile Picture

Muhammad Shahzad Sh... 51 Most Valuable Professional

#2
Ramesh Kumar Profile Picture

Ramesh Kumar 42

#3
David Shaw_UK Profile Picture

David Shaw_UK 27

Last month Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans
Liquid error: parsing "/globalsearch/?q=call++bomber" - Nested quantifier +.