Akira Honma (Japan Concentrix KK)

On "Expense Estimate" tab in a project record form, users must manually a record one by one.

When creating "Expense Estimate" on it, it takes some to process.

Users would like to register multiple "Expense Estimate" records on it, but it takes a huge time.

It would be great for users to have a feature to import or register the records in bulk on "Expense Estimate" tab in a project record form.

Currently, when SQL servers have a problem, users cannot access data in their organizations.

When users unable to access data, users cannot know what is happening as the error message says "SQL server error occurs" and users have no idea about what causes an SQL server error.

If the problem comes from Microsoft Server, some messages should show up to let users know what is happening.

It would be great if some messages such as "Microsoft has been investigating the problem. Sorry for you inconvenience" show up when the server error comes from Microsoft problem.

Currently, as the URL below says, environment to environment migration for Word or Excel templates isn't currently supported.

URL: https://learn.microsoft.com/en-us/power-platform/admin/using-word-templates-dynamics-365#download-the-template

Sometimes, environments migrations are useful when using same templates.

It would be great if environment to environment migration for Word or Excel templates would be supported.

Regarding importing resource on Time Entry, if a task on a project record sets 0 on duration, the task is only displayed on that task start date and finish date is ignored.

Users might miss and cannot import the proper task due to this behavior when importing resource on Time Entry.

This behavior is currently by design, but this should relate to actual task finish date.

It would be much better if task duration precisely matches the display when importing resource on Time Entry.

Currently, we cannot customize "Utilization" table on "Project Operation" model driven app on make.powerapps.com .

This is expected behavior, but the error message below is displayed when we try to customize this, which is not user-friendly for some users.

Error: 

Failed to read a named property "UiTestGlobal" from "Window". Blocked a frame with origin "https://~~.crm.dynamics.com" from accessing a cross-origin frame.

It would be great if the displayed message is simpler to understand that this table is not customizable.

Also, it would be more user-friendly if we could customize the "Utilization" table on make.powerapps.com without any errors.

Views (grids) in model driven apps cannot filter by using other field values so far.

For example, there are A and B date only fields on a table, but filtering below cannot be set by default features.

Field - Operator - Value

"Field A" "Older than" "Field B"

This feature can bring users more options to filter.

It would be more convenient if filtering using other field values is available in views on model driven apps.

Currently, FetchXML cannot change the data type on query.

If we could change the data type on FetchXML, it would improve the customization user can change for complicated query to be applied to each user operations.

It would be much better if we could change the data type on FetchXML.

Regarding enabling or disabling this "Focused View" setting, there is only per organization level settings for now.

Some users would like to change the settings depending on each app.

It would be much better if "Focused View" setting could be switched by each app.

Currently, there is a difference between Teams on Dynamics 365 and Microsoft Teams app about searching users.

On Teams on Dynamics 365, if "User Type" is empty on users regarding Microsoft Entra ID, user is not searched.

In addition, user search behavior is different depending on places where users are searched on Teams on Dynamics 365, which sometimes confuses users.

It would be more convenient if search behavior on Teams on Dynamics 365 is same to Microsoft Teams app.

Regarding Dynamics 365 Project Operations, currently, there is no default feature to automatically relate roles from selected bookable resources when creating project records.

When creating Project records, according to selected bookable resource records on "Project manager" fields on the form, team member is added to the created Project record.

The role of this added team member would be always "Project Manager" instead of related roles from selected bookable resources.

However, some users would like to set related roles when creating project records.

It would be great if related roles with selected bookable resources could be set by default features including Power Automate.