Power Platform Governance and Administration

When using business rules, you can set Owning Business Unit based on a rule. However, it uses the GUID value, so when promoting to Test Or Production, the GUID is different, meaning the rule wont work. I imagine this is the same with any other lookup. Would it be possible to build in functionality to select name versus the GUID value for the lookup. Alternatively, you could provide the option to lookup an Alternate Key value instead of the built-in functionality. That way, we can make a business rule to set a field based on alternate key instead of primary key field. Advantage here is that alternate key is unique by design, so it should work across environments.

Thanks,

Matthew

Currently, users require the System Admin role in order to modify elements of the Synapse Link to DataVerse (such as adding new tables to the export list for D365 F&O). This gives far reaching privileges well beyond the scope of Synapse Link to DataVerse. It would be beneficial from an IT governance stance if an additional role/privilege was added with specific permissions around managing this without giving wider access/permissions.

Feasibility to add From from Email Activity in All My Activities View

Customer Reported Concern

We frequently run in to issues while deploying our custom solutions because Microsoft updates are going on in either the source or target environments. We need to be able to set a maintenance window for all environment not just production and we also need to be able to restrict the days or be altered as to the planned day updates are going to happen. Having a window 7 days a week that Microsoft can use doesn't allow us to plan deliveries without conflict. We have had several Production deployments in a row that were delayed because of updates happening by Microsoft. Given these are our environment we should have a say in the update windows. Microsoft should not only plan the updates but notify us of the planned date so we can communicate if we need them to move it out, primarily for Production deployments.

There should be an option filter on the list of available Word Templates while generating the Word Template from the entity list view or main form. It will enable the end business users to easily search the required Document Templates to be generated against selected record from list view or against the record opened in the main form.

The current experience for managing Power Automate Flows is frankly horrific.

You go into the Power Platform Admin centre and choose Flows and then you have to keep selecting "Load More" until the thing runs out of steam without showing all flows within an environment.

Why can't it just populate the full list of flows immediately?

When you do anything to a selected flow you are then dumped back tot he first 25 flows and have to go through the whole "Load more" process again until you again run out of steam.

This is NOT an administrative tool - it's a vexatious pile of tosh!

Perhaps some of the fine minds at Microsoft could be employed to improve this and make it a useful tool.

Would it be possible to get a clear road map when controls/features are being deprecated? E.g. said control is being deprecated, replace with this control?

In the Spring Wave release we were made aware of controls being deprecated. Some we don't utilise but others we have used extensively across the environment. The documentation said from April 2023 the controls wouldn't be available to add to new form changes, however we've still got them available if we wanted to add new form amendments.

When I've asked for clear defined dates of replacement, no one from support could tell me other than it would be from April 2024. Luckily the controls are still working at time of writing.

The controls have no clear replacement so the suggestions I've had are to used basic out the box controls, use the PCF Gallery or develop our own PCF controls. Development or using third party controls seems risky as its another thing we will have to keep on top of when wave releases are applied, as there is no guarantee the control will be supported after the next release.

When someone has a link to a Power App and they either do not have access or the proper license the error message is not intuitive to the client. Clicking the access request button will some times work. It would great if we could customize these messages to point them to a SharePoint site, person, or some simple additional information.

There is a prompt for when a person does not have a Power Apps premium license to request one at the click of a button. It would be nice to either remove the notification or to be able to update it with our own content such as a link. The "Request licenses" button could go to where we have people purchase the license. The current method is confusing people on where to go when it does not work.

I just recieved an email from one of our business users with a screen shot of our DLP policies with my name on all of them. It would be great if we could keep people from opening the PPAC entirely. Understand that this might help with System Admins of an environment, but we do not want them having that role and we do not want them to have even view access to the backend.

If other companies want to allow their business users to view this information, can we make it an option and allow us to flip a switch to remove access?