Share your ideas and vote for future features

Hi,     this one is based on the community thread here: https://powerusers.microsoft.com/t5/PowerApps-Component-Framework/Default-values-for-quot-input-quot-properties/m-p/304226#M427     It might be useful to have the ability to define default values for the PCF control "input" properties AND to show those defaults in the form designer when adding the control.      I am guessing default values could either be added through the manifest file:     <property name="test" display-name-key="test" description-key="test" of-type="SingleLine.Text" usage="input" required="false"  default="default value"  />     Or from the code...     And those default values should also show up in the form designer whenever somebody is setting up a custom control for an attribute on the form (so it would be obvious what the defaults are) ... View more

Several times now when designing forms, I have found myself wanting to fill additional unused space with larger inputs such as a multi-line text box, however as seen in the following example, this is not possible with the current row/column restrictions -    Ideally I would request a CSS-Grid like implementation, but I suspect this diverges too much from the power user-friendly approach of PowerApps. Instead, I would suggest something along the lines of  'column split' and 'row split' buttons, which I have illustrated below - This would enable much more dynamic form control overall, and could be hidden under the ellipsis easily. Regarding interaction with the split within the field property control, I would suggest two nested lists under the new control, on which fields could be dragged from the parent list. ... View more

  It would be helpful if there could be a system-generated "cancel button" when a form on model driven app is created. Just like there is a save and save/close button already inbuilt on PowerApps.    This would lead to less complexity instead of  building another canvas app and then embedding it on the model driven app.   Hoping Microsoft adds this a feature. ... View more

Please consider adding support for global notifications in model-driven apps, that would be visibile from any place in the application (forms, views, dashboards, etc.) and on any type of device, including mobile. Today, notifications are only supported at the form level with the setFormNotification method. Business case for global notificiations: Compliance: to display a permanent warning to users of the application on how they should use it. News and adoption: to push information to users (e.g. to warn users about a potenial application maintenance downtime, to push usage tips, to remember about particular marketing operations and offers "10% off on this product this week", or to remember to update their opportunities, etc.) Examples of rendering: At the form level (this is the only case where this is already supported): At the view level: At the dashboard level: On other types of pages / web resources: User Experience: When multiple notifications are present, they are collapsed and must be expanded in this manner, in order not to disrupt the user experience (which is good): ... View more

When the base language is not English, in my case it's in french, All the label are not shown the the default language.   Tabs shown are not the label, but the Tab name. The custom feild are shown in the right language, but not the Oout of the box one.     I dont whant to translate the solution because the new interface is not showing the right labels. ... View more

Currently there is no way for the Client API to navigate to a different part of the sitemap.   There is an undocumented way of doing this: Xrm.Navigation.navigateTo({ pageType:"entitylist", entityName:"contact", viewId:"xxxxx", // Optional if you want a specific view viewType:"1039" // Optional if you want a specific view } Please can we have this supported because using openUrl creates a very jarring UX for the user because a new window opens and the client browser back history is not maintained.   ... View more

On the PowerApps Maker screen. When I select the Solutions options (left menu), I'm able to sort on the list of solutions. But once I've selected my solution and see a list of my solution's components, I am not able to sort - this makes it very sifficult to find items - please add sorting to this view. ... View more

Include all columns in a table instead of just the primary key in the views and forms. If based on a model, the generated form should honor table relationships and use an appropriate control to display fk-pk value. These and other similar functionality will make it easier for novice user to have a startup app that they can then use and remove/change functionality they don't need. For experiences developers, it substantially reduces the mundane work. ... View more

There seems to be a bug in the new View editor where it is not allowing me to filter Roll up fields.  Switch to classic view editor and all is right with the world.    ... View more

I would love to see the ability in PowerApps to have tenant-level variables and potentially a collection. Doing so would give the ability to parameterize common items used across all applications like logos, color schemes and user logic.  ... View more