Power Platform Governance and Administration

When creating or updating Contacts in D365, there is a drop-down option for Gender. The current selection only allows for Male or Female. This should be updated to include Non-binary and/or Other.

The Standard on Web Accessibility for Government of Canada websites and web applications requires that each web page meet at minimum all five WCAG 2.0 conformance requirements. At ESDC, conformance with WCAG 2.1 is required. Under WCAG 2.0 Guideline 2.2 Enough Time 2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true: (Level A) • Turn off: The user is allowed to turn off the time limit before encountering it; or • Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or • Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or • Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or • Essential Exception: The time limit is essential and extending it would invalidate the activity; or • 20 Hour Exception: The time limit is longer than 20 hours. In this case, the real-time or essential exceptions do not apply. The 20 hour exception does not meet IT Security standards since it leaves the door open for attacks (session hijacking etc…). For that reason, common timeouts range from 15-30 minutes for low risk applications. This leaves only three options available to meet accessibility standards; Turn Off, Adjust or Extend. None of these options are currently supported with Power Apps Portal. We are requesting that this accessibility issue be brought to the Power Apps Portal product team and request that they consider a design change for a future release that would implement one or more of the options for a portal user to adjust their session.

It could be extremely useful to have different views over the solutions in make.powerapps.com, filtered by publisher. This will help us filter out for example solutions installed by Microsoft (e.g. Marketing related) that often clutter the solutions area.

When we upload a file to SharePoint directly with the same name, SharePoint would ask if user would like to replace the file or keep both (in this case SharePoint would add extension number in the end of the file.) When you do the same behavior in Dynamics SharePoint grid, it has an ‘Overwrite existing file’ option which defaults to ‘Yes’. We’ve tried setting overwrite to ‘No’ however it gives an error. Can we make the Dynamics 365 SharePoint integration following the same behavior as SharePoint natively and keep both files appending (n) at the end of the file

An email is sent to the administrator when the remaining capacity of each area of the database/log/file is now 15%, 5% or 0%. https://docs.microsoft.com/en-us/power-platform/admin/capacity-storage#do-i-get-notified-through-email-when-my-org-is-over-capacity However, depending on the customer, even if the log area is insufficient, the database area may be used to make up for it. In this case, the tenant is not lacking in capacity and the customer does not need immediate action. We would like the following features: -Notify us by email when the total value of database and log capacity is insufficient -Customers can customize email thresholds

We need an option to selectively delete the audit log records related to a particular Dynamics 365 record (e.g. account, contact...). Currently, we are only allowed to delete either the whole audit log partitions (blocks) or delete all logs related to the target records (DeleteRecordChangeHistoryRequest sdk message can be used for that), but it would be great to allow users to choose which audit logs to delete or keep from the record level.

When using a PowerApp to modify records in D365, the records "Createdby" and "Modifiedby" display the owner of the PowerApp instead of the user of the PowerApp making the changes. It would be helpful to have a feature added in PowerAutomate where the Flow PowerApp trigger could be set to run as the user of the PowerApp instead of the Owner. There appears to be no settings to do this on Flows triggered by a PowerApp as compared to Flows triggered by Microsoft Dataverse.

While doing bulk update of case records, header field is selected as default. This will mistakenly update all the bulk records. This field should not be selected as default.

In muliti-language environment with 2 or more supported portal languages the language code is deciding which KA will be shown. If de-DE is changed to de what is recommended, no German article will be found. The same effect is English, changing the code from en-US to en It seems a hardcoded relation between language code and KA language existing. Please improve this behavior by add a new field with KA language in Portal Language definition or define a own search view for each language so it would be more flexible to set up the query. In German: all German and English articles are shown In English: only English articles are shown

If you want to create a new record, you need to change the form from the form selector to create the record. However, if a function that automatically transitions to a specific form when [+New] is clicked while a specific view is selected is implemented, business efficiency can be improved.