Dynamics 365 Field Service

The new schedule board can only display 14 days on the Gantt chart. This is completely unworkable for our application, as we must have at least 180 days of bookings viewable at any given time.

HI Team,

We 've seen few changes in terms of Embedded Power BI Dashboard in Dynamics Issue after wave 2 release.

1.  when we using Power BI Dashboards within Dynamics 365 Since last week, the Power BI Dashboard behavior changed where if user interacts with the Power BI Dashboard within Dynamics 365, like clicking on a row or clicking a filter, it will auto pop up the power bi in a pop up window
2. User need to scroll when opening a Power BI Dashboard to have the dashboard render to the user. 

These are the above 2 changes we observed. Could you please get these fixed where it works like previously? keeping user experience into consideration ?

Currently on the mobile only 4 buttons on the footer are supported (including the grouped list).

This needs to be configurable or expanded to allow more based on the device being in portrait or landscape mode. For example in landscape mode (on a standard ipad) this footer could support approx 8 action buttons before needing to collapse the buttons into a list that requires additional clicks for the user.

On large width screens (curved) we are noticing the resource filter panel consumes a lot of space. It appears to be set as a percentage of the screen size and becomes impractical on larger screens.

The size of this panel should be configurable like other panels on the screen. Users are looking to keep this panel open for ease of filtering, but on large monitors its not feasible due to the real estate it consumes.

Currently we are using both Individual resource requirements (single resource) and Requirement Groups (multiple resource) for scheduling work. We have also configured booking rules associated with booking creation. These booking rules are only triggering when bookings are created via individual resource requirements and not Requirement Groups.

For consistency in the product this feature should also be extended to incorporate requirements group bookings.

Currently Microsoft gives an error when trying to export data to excel from an unrelated column in a view.

An error has occurred. {1}{0}

Error code: 0x80040216

Session Id: 81c803f1-9f5d-4948-b6f0-72ab00fb5666

Activity Id: 694c956f-21e7-4642-a094-884b7664f0ce

Ideal solution would be to enable this behavior.

On the agreement booking setup we can set a prefered resource and a prefered start time. The naming for those fields leads me and the users to think that the system will be smart and schedule the order around the start time you set when the technician is free to do work. This is specially confusing since we also have the fields pre/post booking flexibility in the same section, leading us to belive that the order will be scheduled in "prefered start time" +- pre/post booking flexibility.

The ideal solution would be to improve the functionality to take technicians schedule into account but changing the naming would also help.

Users would like to configure the layout of the schedule board by undocking the panels and moving them to different screens or arranging them in a different order to suit the user. Currently users are opening multiple versions of the schedule board across different screens whilst adjusting the size of the panel accordingly to support their need (eg: map, gantt width). Doing this requires them to manually refresh each screen (or wait for the timed updated) to see updates as they don't maintain context.

Being able to undock items like the map and move it to a different screen, would allow users to optimise screen real-estate along with additional flexibility for layout.

Mapped fields - When you run an app in offline mode, mapped fields aren’t prepopulated when you want to create a follow-up work order or create a new record from a table that has fields mapped to another table.

For people working in service it is common to have a shift pattern/cyklus. For example week1 you work between 8-17, week2 between 15-24 and week3 between 00-08.

There is not a smooth way of doing this in D365 on the resource working calendar since you can only define 1 week work pattern.

If you have 5 different shift patterns it is a huge manual task to update those template calendars since you have to update week by week.

You should be able to have pattern for several weeks and then update the workcalendar based on from date-todate.

Look forward to hear from you!

Best regards

Inger Lise Vågen