Power Platform Governance and Administration

Currently when administering teams of an environment a user can only sort on Name

You cannot select a view to show only access teams or owner teams like in the legacy advanced settings

Provide at least filtering on team type to allow easier administration

I have been working with Power Fx Formula Columns in Dataverse and as of now it is not possible to use the ^ operator. My customer has a mathematical formula where the operator needs to be used. With this limitation we need to create a plugin instead of just using a powerFX field.

Link to documentation: Work with Dataverse formula columns - Power Apps | Microsoft Learn

Add a section for custom pages in PowerApps.

Either as a new tab in apps, a new nav item, or just mark it as custom page within apps.

This way, you can avoid having to open the MDA that the custom page is in or for it to be in a solution to edit or delete the custom page.

Greetings and good day

Here is my situation:

• I have created a PCF component
• Inside the PCF I have 2 CSS files as resources.
• i published my PCF and imported it in different environments
• In my next Update, I changed those CSS files, but to my amazement the files in Dataverse do not change anymore
• No matter what I did, those webresources are Managed and not subject to change.

So in summary, WebResources in PCF components are unable to be updated, you developers better watchout and you microsoft developers, you can fix it for us.

Currently the power portal gives you time in UTC time zone when you use the liquid tag. If we had the option to change the time zone to the time zone that we are in that would be great. It is a basic request and its strange that there is no current way to do this.

When ever I get the current time using the liquid tag {{ now }} it gives me time in UTC. I cannot add/subtract time from this value either.

Dynamics restore from backups ruin Append Mode Synapse links.

If you have synapse link in Append mode (to keep history)

The following scenario has no reasonable options for keeping history.

1. a D365 backup is taken (versionNumber is up to 10)
2. a production release to D365 goes wrong (versionNumbers up to 20)
3. within the release window a restore to backup to point 1 is done.

When this occurs

1. the synapse link (the internal Dsf subscription) is removed
2. attempts to create the new link fail due to a non-empty target storage container.
3. you have to erase the existing container to re-establish the link.
4. when you re-establish the link, the next update has a versionNumber of 11, duplicating values which occurred after the backup was taken (11-20).

Step 2/3 means you can not preserve history though this scenario.

Step 4 means that after you restore from backup, anyone who has consumed the old data now has two copies of versionNumbers 11-20.

Feature request

1. some way to preserve history through a dynamics restore from backup
2. when d365 restores from backup, please do not reduce the versionNumber back to an older value but keep it continually increasing over time.

When we try to search something on the Power Automate Desktop console, the search result(under “Find in flow”) will disappear after we edit one of the step and save. Please refer to the screenshot below. Please help to take this back to product team as voice of customer and let us know if it’s possible to be realized in future releases. 

Currently when users launch for the 1st time then they are taken to the sub-area they have selected as their default in the personalization settings. However, after 1st launch when they move between the areas then they are always taken back to the 1st item in the navigation, which they might not be interested in.

So, can system do the following:

1. When switching between areas, system checks if the Pane is the one selected in their personalization setting and if yes, then take the user to the configured Default Tab.
2. If the Pane is a different than what's configured in the Personalization setting then take the user to the 1st item in the navigation for the area.

There is an available option to disable self-serve environment creation. That means a service admin has to create environment and assign to client. However, currently, once a dedicated Power Platform Environment is assigned, that client can then enable dataverse even if they don't plan to use. We have seen MANY MANY instances of people checking the dataverse checkbox and then doing exactly nothing with that service.

Please add a admin-only option to the dataverse enablement for the environment owner/admin ensuring that only a service admin can enable dataverse on each environment.

Within Dynamics 365 the bulk delete tool is very useful but does not allow the setting of a criteria as a lookup to another table does not contain data, it does allow selecting a view of this type but does not respect the criteria without warning.

We have a number of regular deletions we would like to conduct that would include these criteria so are having to use third party tools which are much slower to complete them and with less automation.