There is a tool called Access Checker to check the access rights to a record. https://docs.microsoft.com/en-us/power-apps/user/access-checker   This tool is available to everyone, but System Administorator is the only user who can search for users. Please add a function so that users other than System Administorator can also search for users.   This is because system administrators are not the only ones who manipulate user privileges. There is a need to set up an administrator for each BU and operate it as a near system administrator who manages access rights to user records. ... View more

PowerApps can currently "move the controls with the tab key," but it does not implement keyboard navigation features.   There are still many users who prefer keyboard operation to mouse, and I would like to add that function to the screen of PowerApps like other web screens ... View more

Currently, the components of any app downloaded through AppSource can be edited by going into the solution package or by tracking down the components' locations, even for managed solutions. This means that the source code/logic/formulas used for any of the components (such as Power Apps or Power Automate flows) can be accessed by administrators.  This means that any user could theoretically download an app, rebuild their own version using the source code/logic, and re-sell the app to others. This could scare off potential users of the AppSource platform since there would always be an inherent risk of piracy for their proprietary work.   Please see the attached images.   My idea is as follows: if an offer on the AppSource marketplace is examined by a team of Microsoft experts and granted the Microsoft Preferred Solution badge, the app owner should have the ability to prevent all source code/logic/formulas from being viewed (perhaps by preventing components from being directly edited). The badge should make this reasonable since Microsoft has verified that there is no malicious code/logic/formulas within the solution, which means that the customers should have peace of mind and have no need to go into edit mode. All data source references and connections should be handled through environment variables that the client would set during (or shortly after) app installation. ... View more

In PowerApps you can define a custom connector that uses environment variables in its OAuth security settings, but users running the app can't access the connector. After some testing Microsoft determined in case 2203090010000140 that use of environment variables this way is currently unsupportable and is a product limitation.   The request is to remove this limitation and support environment variables in the OAuth settings.   Custom connectors are the gateway between apps and REST APIs. This opens up the PowerApps world to using APIs beyond the standard connectors, something that is a significant need in business systems. Businesses also need to secure access to APIs, and OAuth securest option currently available in PowerApps custom connectors. Businesses also want to automate releases through pipelines and ALM without manual steps. Without environment variable support in custom connectors deployment has to be manual and less secure.   See also Custom connector OAuth with environment variables fails in canvas app    ... View more

When outputting CSV from dataverse, "Create by" columns, "Choices" columns, etc. are not output, and it is inconvenient to reuse the data, so please make it possible to output in complete form. ... View more

As we know from the "known limitations" on MSDN [https://docs.microsoft.com/en-us/power-apps/maker/canvas-apps/git-version-control] , Co-authoring feature does not work with on-premises Git repositories. However, there is demand for Co-authoring feature for on-premises Git repositories among customers who use Git Enterprise Server on private cloud.   It would be very nice to have this feature for on-premises Git repositories. ... View more

We usually encounter a scenario that we have many duplicate records and wish that the Merge function can merge all the records at once instead of just two duplicate records. With the current merging method, it takes us very long time to finish our work. There are external resources which help us to do so. However, it will be even better if CRM has that function. ... View more

I would like to be able to restore a canvas app other than "Restore Version". This feature would allow me to restore the canvas app when "Restore Version" does not work, so I can react quickly when a problem arises.   I need this feature. Please vote if you agree. ... View more

If you save a dataverse record via SubmitForm in a Power App, the dataverse keys are not taken into account. If you have defined keys in Dataverse (to prevent duplicate records), they should be taken into account. Currently this is ignored and you can create duplicate records. The defined keys on a dataverse table are ignored. The sense of the keys is made useless.   ... View more

Currently Connector action control in DLP is available only for connectors that can be blocked. It would be good to have an option for example for O365 Outlook connector to block action "Delete email", while leave option to "Send email" or "Read emails". This is currently not possible for non-blockable connectors. ... View more

In the latest version you have added the rich text in the portal and it works just fine.    The problem about it is that the "Comments" pop-up is not a form, it is a hardcoded web resource defined on the basic form metadata of type "Timeline". As such, the rich text editor is not available to be added on this pop-up, as we cannot customize it.   Unfortunately the comment entity is not even a “regular” entity, only a support one for this feature. So we wouldn’t even be able to add this relationship. This “comment” option is really a very specific feature and cannot be used as other form fields.   It is very important to us to add this rich text into the comments on the portal because our hundreds of clients and partners need to add several screenshots in the comments (not only one) and also because they want to send a story about their comments, for exemple, when they want to give an specific exemple they describe the case with an image and continue describing with another image so it is clear for the technician to solve their errors.    Please take in account this request for your next version.   Regards,    Sewan       ... View more

We would like to be able to determine if a feature we are currently using is a preview feature. This feature would allow me to work more quickly to determine if a feature I am using without knowing it, such as "the ability to connect to an Excel file on a SharePoint site" is a preview or not.   I need this feature. Please vote if you agree. ... View more

The formula bar in the Power Apps studio already does syntax highlighting, IntelliSense and has options to format/beautify Power Fx formulas.   It would be great to have similar capabilities in Visual Studio Code, as formulas are recognized as Plain Text today. Making edits or reviewing code within VSCode is something professional developers often do. As Power Fx has moved to an open-source language, this would also be useful for use cases beyond Power Apps. ... View more

# Background: I have created a test list, and added a standard out of the box Date and time column. The SharePoint list is set to (UTC) Dublin, Edinburgh, Lisbon, London. I integrated the form (Integrate > Power Apps > Customize form), and added standard out of the box DataCard with DateValue property set from Local to UTC (Properties > Date time zone > UTC), as I want the date to be stored in UTC.   # Behaviour: While creating a list item and put the date/time in the picker 2:00 am. When I save it, it is adjusted automatically for me and it is displayed back as 3:00 am. When I go back and edit the list item, the DatePicker automatically changes the initial value and changes it to 05:00 by adding two additional hours, as shown on the screenshot below:   If I save and edit the list item again, the DatePicker again changes the values and adds two additional hours:     My understanding is that the Power App is making the adjustment, because it is taking actually the browser/machine system time zone. However behavior is incorrect, because the Date/time card is set to UTC and should save and display back the time in UTC. In addition, the initial time value in the list item shouldn’t be changed when the list item is being open to be edited again.   I was in contact with the PowerApps support and was provided with the workaround to update the DataCard with some expressions in order to convert between local time and UTC. I was told as well that this is not a bug, but rather a limitation in connection between SPO list and PowerApps. The TimeZone property of the DatePicker applies only to that control, and the dropdowns are not affected by the change. The TimeZone property was added long time ago and the Data Cards were introduced at later point, so updating the expressions on both the date picker and the dropdown controls was the only way to make this scenario work.   In my opinion this is a design flaw that should be corrected, the reason being that just selecting standard capabilities (out of the box date/time card) it can lead to a data corruption.                 ... View more

I would like the ability to export Dataverse columns, etc. This feature would allow us to compare, etc. and work more quickly when our predecessor is no longer available. I need this feature. Please vote if you agree. ... View more

Could you please allow "Microsoft PowerApps Office Add-in" to be installed offline? According to our system department, it seems that installation from the Office Store is not permitted due to security reasons, and I requested that it be available for offline installation.   ... View more

Hi everybody,   I would be happy, if I could have a visible border for input fields inside a formular that are in view mode. Like by specifying for example a DisabledBorderThickness or something.   What do you think? ... View more

In the modern form editor, when adding a subgrid component, you are by default presented with the option to select any table. To only show tables that have an actual relationship to the current form's table, you need to tick the box "show related records". In practice you ALWAYS need to select this. Ever since 2011 when the subgrid feature was introduced, I don't think I've ever ran into a requirement to show records from another table on the form that have absolutely no connection with the current record. I believe ~99% of app makers are therefore required to now remember to tick the filter box, so that they don't need to browse through all the thousand tables within the environment. Besides, since there is now a table named "[Deprecated] Dynamics Customer Service Analytics" in every environment, it is alphabetically sorted to be the first thign every app makers sees in the subgrid configuration experience. All of this could be easily hidden if the "show related records" filter would be on by default. ... View more

We can already drive most security configuration from outside of Dataverse in Azure Active Directory (AAD) through group teams, but we can't assign a business unit to a user without a manual intervention on the environment.   Workarounds exist, but they involve implementing custom logic.   Business unit assignment to users is a crucial piece of Dataverse security modeling, as the records created by a user are by default owned by the user's business unit. Also, as all users are created in the root business unit, this means that without any configuration, all records are by default owned by the root business unit. Ask is to support user business unit assignment from Azure AD security groups. ... View more