Power Platform Governance and Administration

Expand the current reports on Power Pages authenticated users and anonymous users with the following info.

Providing admins with better insights wether the numbers shown in the report are correct and that they know where those numbers actually come from.

Authenticated users:

• Contact GUIDs
• date and time on which the contact logged in

Anonymous users:

• IP address or some other identifier on which an anonymous user is registered.

We need Business rules to work when we select Choices Column with multi select option.

Our requirement is to hide/unhide sections in the form, dependent on the value selected by the user from the Choice Column(multi-select). However, when we initiated the creation of the Business Process Flow (BPF), we were unable to locate the Choice Columns for creating condition.

We need this functionality to be added in the product.

The 'Name of Record' record identifier (activity Id) matches the 'Invitation id'

If the Update action failed, because of Flow design work, it triggers mechanism of the Flow that cause the error. Basically, it will create a new record with the same id follows the upsert process as stated in the following documents.

And when a new record is upserted, due to having the same id as the previous invite record, this record will be detected as having duplicate key matching the ‘invitation id’ mentioned above.

Reference:

https://learn.microsoft.com/en-us/power-automate/dataverse/update

• https://learn.microsoft.com/en-us/power-apps/developer/data-platform/use-upsert-insert-update-record?tabs=webapi#understanding-the-upsert-process-for-standard-tables

Values set in Choice-type column have a Description field.

This field does not seems to be used but could be used in model-driven apps and canvas apps to provide a tooltip explaining what a given choice represents.

This would be useful for fields where a tooltip could guide to new employees to use the appropriate value for a given record.

For example, when select something like a case type or a lead type, if the user is not sure what value to set, they can try a value and hover over the field to see the tooltip to help confirm that they have selected the appropriate type for the record.

Currently, it is not possible to extract what operations are generating requests in the Power Platform Request Report.

If we can extract what operations are generating supply, we can avoid generating unnecessary requests.

In Dynamics you can read an email without ever having to pick it which leaves a gap in the timeline from an audit perspective. This makes managing queues difficult because there is no clear audit trail which allows Managers to address items not being worked on by partners across regions or on shared mailboxes, with partners choosing which cases to work. We would like there to be an audit trail indicating the time an individual opened a case/email.

A clear indicator through audit so if a case /email was picked by partner even if no change is done to the record  

The editable grid currently has a number of column type limitations. These should be remedied, and all column types should be allowed to be editable. At the very least, the Status/Status Reason columns.  (https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/make-grids-lists-editable-custom-control?view=op-9-1#data-types-that-arent-editable-in-an-editable-grid)

Currently when editing a basic form in Power Portals/Power Pages there is a checkbox that when checked enables the end user to attach a file on the corresponding entity. When that option is enabled , the label "Attach a file", the button "Choose files" as well as the label "No file chosen" next to it appears. Even though there is an option to add translations for "Attach a file" there is no option for other two. That would be help especially when multi-language is enabled for Portals.

According to MS public information,the only way to map table columns is to use solution explorer (classic designer).

Title:Open solution explorer

 URL:https://learn.microsoft.com/en-us/power-apps/maker/data-platform/map-entity-fields#open-solution-explorer

But according to another public information,classic app, form, and view designers are deprecated.

Title:Classic app, form, and view designers are deprecated

 URL:https://learn.microsoft.com/en-us/power-platform/important-changes-coming#classic-app-form-and-view-designers-are-deprecated

So,I hope that it will be possible to map table columns using modern designer.

Single sign on for Custom connector, so that any update in credentials should automatically be updated like any other connectors (eg dataverse, outlook or onedrive)