Power Platform Governance and Administration

As a Power Apps user,

I want each Power App (like Customer Service, Field Service, etc.) to have its own unique favicon,

So that I can easily distinguish between multiple apps when multiple tabs are open in my browser.

Acceptance Criteria:

1. Distinct Favicons: Each standard Power App should feature a distinct favicon that represents its unique function, replacing the generic Microsoft logo currently used.
2. Customization Capability: Users creating custom apps should have the ability to assign a custom favicon to their app to ensure visual consistency and ease of identification.
3. Visibility: Favicons should be clearly visible and recognizable even when browser tabs are minimized.
4. Implementation Across Environments: This feature should be implemented consistently across all environments where Power Apps are accessible, including different web browsers and operating systems.

Business Value: This enhancement will improve navigation efficiency and reduce time spent searching for the correct tab, thus enhancing overall productivity and user satisfaction.

Improve the inconsistencies and gaps in the data in the Power Platform Admin Center downloadable licensing reports.

See: TrackingID#2404120040012099

We have the possibility to filter the lookup by related rows

You can filter this lookup column based on a row related to both the current table and this lookup.

Select a relationship from the Related row to current table first, and then select a relationship from the Related row to this lookup's table.

(https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/special-field-properties-legacy?view=op-9-1)

It would be awesome if we could have the same thing on subgrids. Show not all and related records, but also filter them by any lookup value that is present on the form.

In the command bar designer, you can define what happens when a command is activated - execute formula or JavaScript.

For visibility, you can only choose between 'Display' or 'Display with condition from formula'. This means that for simple buttons with more complicated display conditions, the entire button must be created using the XRM Toolbox, as the requirements in the visibility rule can only be implemented to a limited extent with Power FX.

This problem would be solved if the visibility could also be defined with Javascript.

Currently, the Power FX function 'User()' is not supported in model-driven apps.

This should also be enabled in model-driven apps so that

• the visibility of buttons can be adjusted based on the logged-in user
• the current user can be automatically written to a field via a button
• ...

If a user copies data, e.g. account name, from a html source such as a company website and copies that data into Dynamics it could include the html-character NBSP which is usually is displayed as SPACE for the user. This special character should be replaced automatically with a SPACE for single line text fields.

One problem is that Sharepoint takes that special character also within its URL which could lead to problems using Power Automate with other systems.

Activate the download option for SharePoint documents in the model-driven app. This option used to exist but has been deactivated.

PROBLEM

The Dataverse does not record milliseconds in its date/time columns.

We have various jobs in our source systems (not all under our own control) that produce changes in short periods of time.

In Dynamics we have plugins that attempt to locate and set the "current state" of various entities based on the LAST action taken.

IMPACT

Without milliseconds being available, some entities are set to the wrong "current state" because the code randomly selects one record from the set of records falling in the last second of activity as the entity's "last action".

This can have potentially legal ramifications.

SOLUTION

ALL columns in Dataverse need to support milliseconds.

This includes built-in columns (e.g.: createdon, modifiedon) as well as custom columns.

Allow for management of Power Platform app permissions within SharePoint, for SharePoint integration capability. Goal is to get away from the Sites.FullControl.All API currently used today from the SharePoint integration for Power Pages.

Initial support request details opened for this:

Support request ID

2401240040015793

Issue title

DCR request for SharePoint integration in Power Pages.

Issue description

In order for SharePoint (SP) integration to work, unfettered access to all of SP must be granted to the Power Pages backend Entra App, via the Sites.FullControl.All application type SP API. We have multiple use cases that we as a company are wanting to provide to our customers, in an ISV/SaaS like scenario, driven by Power Pages using it's SP integration feature for document management. We would like to request a DCR be opened for the Power Pages team. Specifically enabling this functionality to work using the Sites.Selected SP API and manage permissions for the Entra App directly in the SP site. This change would be more inline with a zero trust philosophy.

Currently it is not possible to restrict user access to the SQL TDS endpoint. Please update this to allow restrictions for users and groups.