Power Platform Governance and Administration

Today, DocuSign permissions from the DocuSign integration via the AppSource only works at the user level. When assigned to a team, the members of that team do not inherit that level of access. For example, we want our agents to be able to create DocuSign documents via Dynamics 365 Customer Service but gives others in the organization the ability to see them in Dynamics 365. Today, we need to assign that capability on a user-by-user basis. DocuSign has a similar ticket in their queue (DYN-232). Thanks!

When a user gets disconnected from the internet, we would like them to be able to continue to be able to fill out and save forms delivered by power pages locally so that when they re-connect to the internet they can submit it.

1. In the first version, the managed solution was deployed to prod with customisations enabled (as default).
2. After that, allow customisations was turned off and the managed solution was deployed again to prod.
3. As expected, the solution was showing as managed and the app was not editable within the solution, however it is editable in the 'Apps' tab.

I have researched and came across a community forum where other users have experienced the same issue but with no solution other than contacting microsoft support as the general consensus in the community is that this is a bug.

See forum here: https://powerusers.microsoft.com/t5/Power-Apps-Pro-Dev-ISV/Allow-Customization-is-off-and-a-managed-solution-is-exported/td-p/2130014

After assigning a case to a user from the queue view, the paging list reloads and then returns to the first page instead of staying on the page where a case has been assigned from. Can you please stop the queue view reloading, so it will stay where it was rather than returning to the first page. It's so inconvenient to the users who are delegating cases to other team members as they keep losing the position where they should assign the next case. This looks an easy fix but will greatly improve our user experiences. An early resolution would be much appreciated.

Steps to replicate the issue:

Select Queues under Service navigation section to display the queue item list page.

Select Email Queues from the dropdown.

Go to the second page.

Select/tick an email from the list and select Queue Item Details from the ribbon.

Close the Queue Item Details. This will then reload the data and return you to page 1 rather than the page you were previously on.

Hi,

Query throttling can be very costly for customers and they may potentially lose revenue because of the system is purposely slowed down.

I would like to propose features related to query throttling:

1. Provide self-sevice dashboard or chart for customers/partners to monitor the DB performance for the past 30 days. This will help the customer/partner to take action in advance before the query throttling is activated.
2. Provide advance notification to customer/partner that a query may potentially slowed down by the activation of query throttling so that customer/partner can take preventive action.

The above two features can prevent potential lost of revenue for customers due to the activation of query throttling.

BR,

Fredy

With the "Access Connector for Dataverse and Power Platform", data can be exchanged between Microsoft Access (on-premises) and Dataverse (cloud), which is very helpful. Unfortunately, the connector does not support virtual tables of Dataverse, which is a major limitation.

Exchanging data between Dataverse virtual tables (cloud) and Microsoft Access (on-premises) and Microsoft Excel (on-premises) should also be implemented.

At the moment when you export to a Dynamic Worksheet (Excel) you cannot refresh the data as this leads to all the contents of the file disappearing.

There is a "workaround" where you must edit the connection properties, an error is displayed and on closing the window and refreshing the data is displayed, but this is not acceptable for users who need to open the file several times a day.

Previously users were using Excel sheets connected to a SharePoint list, and they had no problems refreshing data so this is a regression for our users.

The UI of Dynamics 365 should allow developers and users to create system and personal view with a filter where conditions linked by "OR" are possible across different related entities, either parent-child or across multiple entities related to the same parent entity. Currently this is perfectly possible by downloading, editing, and reuploading the FetchXML of a query, but not in the standard UI. Queries created by manually editing the FetchXML cannot then be edited in the UI.

It should be possible OoO to create subgrids that show grandchild records, linked in a second level relationship via an intermediate entity, without having to use an editable grid and without requiring creation of an independent relationship to be maintained. This should be possible also in a standard subgrid, not in an editable subgrid, and without the grandchild record to be sorted by the intermediate record.

Finally, for N:1 and N:1 second level relationships it should be possible to display a column in a view, for second-level relationships.

Specifically for the case entity, but more generally for all entities, it should be possible to edit the label of a column in a view, just like it is possible to do that in a form. The current UI would just require a minor modifications: in the 3 dots menu of the "edit columns" button of a view, add a "Rename" option to change the name of that column in that view.