Power Platform Governance and Administration

Ideas:

1. Allow administrators to exclude one day per week to accommodate weekly after hours deploys.
2. Shrink the 9 hour requirement or make it variable so customers have more flexibility to install solutions after hours

Currently, the maintenance window settings for production environments require you to have 9 hours available every day of the week for Microsoft-owned solutions to install. Microsoft recommends administrators deploy to prod after hours. However, with the limited maintenance window settings we have access to, if we deploy at 10pm and open for business at 7am, Microsoft's maintenance window gets in the way and blocks us from importing solutions.

Thanks!

When using the API call to "/api/data/v9.0/organizations", the value for "auditretentionperiod" does not reflect the audit retention period setting in admin center. However, the value is updated correctly for "auditretentionperiodv2", which can cause confusion to customers. The "auditretentionperiod" attribute should be removed to avoid confusion.

In an environment of type "Microsoft Teams", auditing should be enabled to enhance security without the need to upgrade to Dataverse database.

We need to remove the delete button from the form or pop up, if the current user is not having the appropriate permissions, this issue cause confusion even the delete button is not functioning if the user doesn't have the required role.

I am reaching out to discuss the challenges our organization faces with Dataverse space consumption tracking and deletion job progress monitoring. Our inability to reliably track audit space consumption across environments impacts our ability to manage several terabytes of data effectively, particularly in an organization with thousands of users.

Furthermore, the deletion jobs' progress currently lacks informative metrics, such as percentage completed and estimated time of completion. This lack of visibility can hamper our operational efficiency and decision-making processes. Lastly, the execution time for these jobs is a concern, with some taking several days to complete, which is far from ideal. The execution time is not predictable at all. My suggestion is that you publish in your public documentation how this works in the backends, and what is the expected execution time (considering the size of the audit log), so we as administrators can plan when/how to run these jobs. 

Addressing these issues is crucial for maintaining our system's performance and ensuring the efficient use of our Dataverse space. I believe improvements in these areas will significantly benefit our organizational workflow and data management practices.

Currently, the admin should access each environment individually and apply the Version upgrade for each app. Admin should have option to synch and upgrade a D365 App to a single version across all environments in the tenant.

When editing using the Design Studio it only allows editing in the default language. 

In sites with multiple languages designed to use many snippets for localization content editors must use the Portal Management app to edit snippets out of context from the pages they occur on. 

It would be beneficial to be able to toggle the language of the portal in the designer to allow a preview of the content in said language and the ability to edit page copy and snippets in place. 

I don't know how Design Studio was released without the ability to choose the editing language.

Credit to Eric Sutter who first posted this 9 months ago in Power Pages Ideas Forum, which seems Microsoft does not monitor.

Microsoft recently released a new feature to "Block unmanaged customizations (Preview)".

So when "Block unmanaged customizations (Preview)" is enabled, please allow the Owners and Admins with CRUD Permissions for Unmanaged Solution and its Objects.

This will be a supportive improvement related to another idea below

https://experience.dynamics.com/ideas/idea/?ideaid=144f18a9-9edc-ee11-a73e-002248504629

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.

+ New should bring forward the related field.

Repro Steps:

-add a sub grid on a form, from a different entity

-create a new record 

- save

- without closing the record, add another new record by click +new on the ribbon

-save and close 

- save and close

Issue: only the first record gets added on the related sub grid of that form, the second record is not recorded in the related entity, ie, the relationship breaks for every record except the first one.

Business Impact: Users do not understand relationships with data models. They see a "+ New" and they think .... cool I'll just hit this button. They do but when they go back to the subgrid the records are not there. Reaction is "This is broke" If I tell them oh yeah that is by design they look at me funny and if I tell them all they have to do is add the related data again they resist. Ultimately, they do not want to use the product.