• 2

    Characteristic date filtering

    Suggested by Craig Fitzgerald New  1 Comments

    Some professional skills/certifications are valid for specific periods of time and can expire. Currently you can filter resource requirement results by characteristic rating, but cannot check if the resource characteristic is still valid for the date/time returned in the schedule assistant. Manually deactivating a characteristic will only prevent all resource matches from that moment onwards, so bookings might have already been made for future dates before it was deactivated.


    You can filter start/end dates on the schedule board, but these ufx methods do not appear to work on the schedule assistant, so you can only filter by todays date.


    Can either a date filter to be added to the characteristic in the same vein as the rating, or allow the Retrieve Resources Query to support filtering of custom date fields based on the returned results.


  • 2

    ScheduleBoard: Booking colors customizable

    Suggested by Simone Boniolo New  0 Comments

    On the Schedule Board, the booking background color is defined on the booking status.

    The booking status color is customizable, new booking status (with respective colors) can be created, but I need to see background color based on WorkOrderType (installation, Maintenance, Repair,...).

    I'd like to have these colors logic customizable.


  • 2

    Do not update Work Order 'System Status' when the sub-status is changed and System Status is not different

    Suggested by Ian Podmore New  0 Comments

    The current system behaviour is that when a Work Order Sub-status is updated on a Work Order, the System Status value is updated even if it is not different to the existing value.


    This causes multiple triggers of Processes and Flows that are triggered by the change of the System Status field in the Work Order entity.


    Our use case is that we have 2 x sub-status records with System Status = Posted.

    1. Issued for Invoicing - default value
    2. Invoiced - updated later by data


    When the 'Invoiced' sub-status is set, all Processes and Flows that are triggered by System Status = Posted are re-triggered, and the Closed On, and Closed By fields are also updated.


    We do not believe these fields should be updated, as they were already set.


    The requested change is that when a sub-status lookup is changed on a Work Order record, IF the System Status of the new Sub-status is the same as the existing Work Order (System Status) then the System Status value should not be re-written as it is not changed.


    It is not possible to set a direct filtered trigger in a Flow based on a sub-status value as it is a lookup.


  • 2

    View on Schedule Hourly vs Details on Schedule Daily/weekly/Montly - Booking

    Suggested by Alvaro SANCHEZ New  0 Comments

    While Scheduling Service Engineers Interventions, when having a big team, it is necessary to have a larger view of Bookings/jobs such on weeks or months. This allows to quickly go back to the job that was scheduled in a period of time and rapidly.


  • 2

    Add option to disable the onclick create new behaviour on the Calendar control

    Suggested by Kunihiko Hayakawa New  0 Comments

    With the following calendar control users can click on a empty timeslot on the calendar to bring up a create form for the entity. Please consider adding an option to disable this behaviour so that users can't create new records by click on a calendar slot.


    Add the calendar control to tables in model-driven apps - Power Apps | Microsoft Learn


  • 2

    Having another booking field like(Customer name) on Daily/Weekly/Monthly view of the schedule board.

    Suggested by New  0 Comments

    My client wants to see customer name instead of start time or duraion on Daily/Weekly/Monthly view of the schedule board. I have already put it on the hourly view but Is there any solution to have it on the other schedule board's views.


  • 2

    Consider a maximum weight constaints for route Optimization

    Suggested by Philippe Kreiss New  1 Comments

    For a waste management scenario with Trucks collecting bins. This scenario can be usefull for every city in the world.


    RSO should consider a Max Weight constraint for the trucks and also the possibility to add a specific drop off site when the max weight is reached




  • 2

    Add adress field on Org Unit to auto populate longitude and latitude

    Suggested by Victor Munthe New  0 Comments

    When working with Org Unit the user have to find the longitude and latitude from, e.g,. Google maps. It would be nice if we had a adress field (as in account) where longitude and latitude is based on that.


  • 2

    msdyn_businessclosure entity is not retrieving data in SSRS XML fetch

    Suggested by Hector Hernandez Hernandez New  0 Comments

    Customer wants to create a Report using SSRS, so they are using the connection type “Microsoft Dynamics 365 Fetch” in Visual Studio thru Query Builder wizard , the idea is paste the XML fetch built in an Advanced find in Dynamics CE. In Advanced find is retrieving data  but pasting the same XML in Visual Studio no rows retrieved, user used is a system administrator in both sides.

    Any other entity is working fine.


    Specific Request: allow msdyn_businessclosure entity to be used in SSRS


  • 2

    Adding Incident type to work order takes time to copy data

    Suggested by Diksha Shivran New  1 Comments

    When a work order is created, incident items such as products, services, and service tasks are copied to the order using the "Field Service - Copy Incident Items to Work Order" (LongJobs_CopyIncidentItemsToWorkOrder (number 464)) system job.

    The documentation says that the system task is a background process and its duration is not specified. The only thing is that it is written that not immediately, but after a while, the elements will be added to the order.

    Is there a way to streamline the process of copying incident items so that items are added as soon as the work order is saved?

    Adding the data to work order takes more time when the amount of data is more.