Power Platform Governance and Administration

Following the release of the 2022 Wave 2 when responding to emails only the "Reply All" button is readily available. One has to click on a drop down menu to use the "Reply" option. We have 100s of D365 Teams integrated with shared event inboxes that we use to respond to customers all around the world in multiple languages. When using the "Reply All" button this causes several issues for us. One, it causes ticket loops since we currently have Automatic Reply enabled on our Modern ARCs. Two, it creates unnecessary emails send back to ourselves when not needed and increasing unnecessary storage. I would like to propose the return of the "Reply" button. At least in our case the "Reply" button is used more often than the "Reply All" and also it eliminates the extra steps needed to use the "Reply" option. Thanks kindly.

We would like to edit the relationship between Opportunity and Quote to avoid ownership cascading between the two entities

Mostly We use Contains instead of Equals options in Filter By in Girds/SubGrids across the D365 CRM. It will be user friendly to make Contains as default option for Filter By component or give ability to configure this default option through Settings.

On a table like Case table, the first cursor location cannot be changed on default function when creating records.

Using "setFocus" by JavaScript can make this happen, but this takes a lot of procedure.

It would be convenient if the first cursor location could be changed on default function.

Within a long-term entitlement, customers must specify the support time available each month.

However, the current feature does not have the ability to divide the available support time on a monthly basis during entitlement period.

When this feature is implemented, it will be very convenient for customers.

Create an entitlement

https://docs.microsoft.com/en-us/dynamics365/customer-service/create-entitlement-define-support-terms-customer#create-an-entitlement

We are in the process of moving from our Data Export Service environment to the Azure Synapse Link and Data Lake. One feature in the Data Export service was heavily used by our reporting was the GlobalOptionSetMetadata table and OptionSetMetadata table.

Azure Synapse Link's Manage Tables does not see these tables in CRM.

It would be very helpful if we could have access to these tables.

Microsoft can deploy new fields on Dataverse Tables at any time, and can do it in Production-type environments before Sandbox-type environments. These unexpected changes in data model can generate issues on applications (having their own constraints) that consume Dataverse.

The suggestion is:

• To have visibility in advance on fields deployed by Microsoft in Dataverse
• That Microsoft always deploys new fields in Sandbox-type environments before Production-type environments

Dataverse Capacity should have more information about the information of each table. Especially for ActivityPointerBase and AuditBase.

These tables can be retrieved some data by running SQL query or accessing via WebAPI. However, it would be more helpful if the Dataverse capacity report could provide more information about storage with filters by column values of each table.