Kunihiko Hayakawa ESCAL ENG

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

On the Field Service (Dynamics365) app the user can see a calendar view when clicking on Bookings. In the top right corner there is a setting that allows a user to switch between the "Agenda", "Day", and "Map" views. Currently when the user first clicks on the Bookings section the Agenda view is displayed by default. We would like to be able to change the default view on a per user basis in this situation.

We are aware that if a different view is selected, this selection will remain the default view for the life of the app session. However, the default view will switch back to Agenda if the app if closed and reopened.

In the Field Service Mobile Xamarin app users could double click the header of a form to expand the form view section to cover the entire app window. Please consider implementing a similar option in the new  Field Service (Dynamics 365) app.

For Time entry records one can use the "Copy row" button on the grid to copy the Time Entry record. Please consider creating a similar button for Expense(msdyn_expense) records.

When the following feature is enabled one can see which users are currently viewing the same record.

See which colleagues are viewing the same records as you | Microsoft Learn

When you mouse over one of these users the following context options are displayed.

Send Email

Start Teams Chat

Open Contact Card

Please provide an option to show/hide each of these menu items.

As per the following document only managed solution imports for embedded powerbi reports is supported.

https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/embed-powerbi-report-in-system-form#prerequisites

------------------

 Be sure to import the changes on your target environment via a managed solution only.

------------------

Please consider supporting unmanaged solution imports for embedded powerbi reports.

It is sometimes very difficult to read a QR code with android devices using Field Service Mobile.

https://learn.microsoft.com/en-us/dynamics365/field-service/mobile-power-app-system-barcode-scanning

The device needs to be at a specific distance and angle for it to read the QR code and it can take a user 30 seconds or so to position their device properly. Please consider improving the read capability in this scenario.

When resetting the value of a lookup field on a editable grid that is already set the options are filtered by the existing value. In order to set a new value the user must first delete the existing value to get the full list of options. Please consider adding an ability to show the full list of options for lookup that has already been set.

When multiple solution import/publish all requests are run at the same time an error occurs as per the following.

https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-apps/solutions/cannot-import-solutions-publish-changes#workaround

The page above suggests using Azure pipelines or Github Actions to serialize the deployment actions but it would be beneficial if Dataverse had an internal queing mechanism to avoid this issue.

Currently there is no way to change the message for OOB dialogs. Please consider adding a user friendly way in which a customizer can change the message for these dialogs.