Takuma Nagano

Currently the timeline has a mentions feature, but there are no user notifications.

In order to be aware of mentions earlier, a notification function would be more useful.

In Teams, notifications can be noticed by sound and Activity, and Outlook has notifications as well.

We are eagerly awaiting the implementation.

We would like to have the ability to specify conditions in a Power Apps table and have it set in detail, such as an error if a column or record that does not meet those conditions tries to be registered.

This should also work when importing from Excel as well.

Example

Let's say you have a store called A and a store representative table called B.

Table B has A in column C.

Each of A and B has a column that controls whether the data is valid.

Each of A and B has a column that controls whether the data is valid in statecode.

We would like to add a function to create a validation item based on the above conditions, and to generate an error in the following cases.

The error message is displayed when there are more than two store managers in one store.

Error is displayed if the store is not a valid store or if the person in charge is not a valid person.

Currently, the ability to select desired columns from multiple related tables and export the data is not implemented.

Since the usual export to Excel, etc., is limited to that table or view, a more flexible selection would lead to improved convenience for the user.

I am currently getting the following error when using the date/time type filter in a virtual table view using SQLServer built on Azure IaaS in a model driven app.

Cannot apply operator ＜ to types Text and DateTimeZone.

\r\n inner exception: Cannot apply operator ＜ to type Text and DateTimeZone.

The above seems to be the current expected behavior, but adding the ability to set date/time type filters would be a convenience to users.

There is a problem that even if a plug-in is used to replace the filter, it is not reflected when exporting to Excel, etc. We would like to see the functionality improved and implemented as soon as possible.

Currently, export and import of personal views is not supported in model-driven apps in Dynamics 365.

A supported behavior for exporting and importing personal views would allow for greater customization and improve customer convenience.