Kevin Quach Support Engineer

Currently, according to documentations, Editable Grid lists are read-only on the mobile experience, I would like to suggest allowing editing on the mobile experience.

Benefits:

• Gives users a wider range of choice for operable controls on the mobile apps of Dynamics
• Allows the Editable grid to fulfill its intended functionality and purpose
• Convenience that never workdon Mobile
• The normal subgrid can be made editable in Mobile, this change makes it seamless for creations that compulse the Editable grid in only a part of the design

I would like to suggest to hide the Copilot for Sales options that are not available for my channel.

Benefits:

• Without the option, there won't be unnecessary confusions, as such options will return an unclear error when clicked on
• Presents the add-in in a much neater way, since there won't be any clustering for unavailable options

Currently, there is a known issue with App icons not updating for Power Apps mobile, it may affect random users or at certain times a group or team.

I request to continue working on this issue as the App icon mismatch affects productivity, due to the confusion created from, either 2 users not seeing the same App icon, or the App icon is not updated.

Resolving this issue will ensure a better experience for all users of Power Apps mobile who prefer unique customizations and personality for their work environment.

Suggestion - There should be a way for the user to selectively and manually resync selective responses from Customer Voice to Dynamics 365

Benefit - Sometimes when there are mishaps and responses don't sync to Dataverse, there is no manual way to resync these records apart from exporting them and creating them again in Dataverse, this is highly inconvenient

It solves - all single-organizational situations that affect only a couple or a selective range of responses, that Microsoft would not run resync on

Currently Sales (formerly Copilot for Sales) has some features in Dynamics 365 CRM that are not available for Salesforce CRM, like Editing or Removing a tracked email,...

Requesting for future revision and implementation of these current integration limitations for Salesforce CRM, as it will open up more options for user with different access levels to the CRM scene.

Currently in the Audit summary view in Power Platform admin center > Environment > Settings > Audit and logs > Audit summary view, the Record column's filter is mentioned to not work at all and will be removed.

This removal brings inconvenience to users as we have to, at the same time, create the filter ourselves or use a Power Automate flow and be mindful of the 5000 records per view limit.

Suggesting to consider and improve the filter function on the record table instead of removing it.

Currently, Unified Routing Diagnostics is communicated to have been deprecated.

The official recommended alternative by Microsoft, Export to Azure Application Insights, currently only offers preview features for D365 Customer Service.

While the feature remains in preview, it is worrisome for users to apply it into our business flows, so users are currently stuck without a Diagnostics tool for monitoring Routing activities.

We're requesting either clearer communication via official documentations, admin messages, ... or a more proper method for monitoring Unified Routing while the Export to Azure Application Insights is in preview.

Retrieve API for Power Platform/CE Apps views currently has a tight threshold so when we have upwards of a million record, the time it takes to load the view increases pretty significantly.

We'd like to request improvement of the retrieve API to reduce the loading time for fetch requests.

Currently the Case Management Agent is only limited to work on Cases that are created via ARC (Automatic Record Creation), which means a complete mailbox and Server-Side Sync set up is required to test the Agent's functionality.

The Agent does not work on any cases that are not automatically created from ARC, which limits testing for modular orgs without proper email integration, like a test org whose integrations will never be used for any other tests.

I would like to request a function for the Agent to allow using manually created (not from ARC) or imported Cases, this allows quicker module testing, saves the hassle of setting up email integration that might just be scrapped later, and allows using a ready sample pool of existing Cases.