As you are working on screens and defining variables, it is easy to loose track of the current value. It would be nice if above the bread crumb in the canvas maker app edit mode there was a small terminal window that showed the current variables (both global and context) and the current value.        ... View more

Currently, model-driven app cannot be deleted by the author. It should be permitted to the author as the actual owner. ... View more

Our design team and UX designers are mostly familiar with Figma to design component for an App. However, our Dev team would like to use Power App to develop the app in the cloud.. Given current features in PowerApp, there is no easy way to import already built Figma components into PowerApp for the dev to add functionality to the component.. Please create a plug and play solution to add Figma components/layers (third party components) into PowerApp easily.. Given this new feature in PowerApp (Figma component import), our design and dev team can work together within PowerApp environment, without replicating the elements of an already built components, which would speed up the App building process in PowerApp by a lot... Thanks, ... View more

Rich text editor should contain Table & image as options to add. Currently we are not able to add table & Image in Rich text editor in PowerApps SharePoint forms ... View more

Dataverse for Teams is great. It helps us to leverage the power of a real database (and more) for the data we store. However, when it comes to automated deployment or general maintenance of D4T apps, you always need to do it manually since there is no/limited API available, which ultimately may lead to errors. Using CI/CD in an enterprise environment is crucial. That is the only thing that currently keeps us from using D4T intensively.   With this idea, I suggest enabling APIs for D4T or offering some DevOps actions with which we could make use of a professional deployment/maintenance of D4T apps.  ... View more

Hi,    If two tables are used for N:N relationship, an auto-generated intersect table is used to store the relational data. This intersect table is not exposed to table permissions. Without this feature, N:N relationship is not useful at all, as the relational data is not exposed. This same data is exposed over CRM APIs using $expand keyword, but is missing from oData APIs.    These auto-generated intersect tables should be available over oData as well, to allow feature parity with CRM APIs.    Thanks.  ... View more

Whenever we use SQL Server connection in PowerApps and share it for users (Read), every user can read Server Name, Database Name and Table/View Name from the connection in Developer tools (F12 in browser). This is a security issue by our company's standards and I would like to know maybe you could work a way to hide this information?   Below are steps to reproduce this case: 1. Create a power app with SQL Server connection and connect data to a table/view. 2. Play the app, open developer tools (F12) and check the Network tab. 3. Clear information in the Network tab and refresh page. 4. Look for Request URL blob:https://pa-content.azureedge.net/3a823424-37b5-443f-a6d9-f17ea650daa4 In the response you will find an URL: @odata.context: "https://europe-002.azure-apim.net/apim/sql/2846f5096cf34a958607fd1f4a3ab4af/$metadata#datasets('SERVER_NAME,DATABASE_NAME')/tables('TABLE_NAME')/items" ... View more

When migrating a solution to another environment or another tenant using environment variables, in Power Apps applications that define environment variables (both sites and lists) as data sources, by changing the internal data of environment variables, it is convenient because you can change the data source of the app without editing the inside of the app.   However, if the data source is updated to the latest state on the edit screen of the application in this condition, information about the token held as the internal data of the application and the data source of the migration source (URL, data source name, GUID, etc.) will result in an error.   However, despite the error, the data source information is over-ridded (confirmed by the internal code of the application) by the internal information of environment variables (two types). The behavior of the application (Data create, edit, delete, etc.) works fine, and the application is migrated in a state where it functions without problems.   We have tried the above behavior with various accounts and tenants, but all have the same behavior, and it is the current expected behavior that an error occurs.   Even though it is used by the recommended method, the error cannot be removed, so we think that the situation must be improved immediately. For example, you can think of various methods such as implementing a mechanism that automatically deletes the data source information of the migration source at the time of export, or implementing a mechanism that filters and removes the information of the relevant part at the time of import and then imports. Therefore, please make improvements to quickly overcome the current situation where errors occurs. ... View more

A simple Time Picker input. 12 or 24 hour option.   But if you want to get fancy: Maybe have it attached to the Date Picker as well. Then based on the DateTimeFormat selected, it adjusts the way you pick. Current Date Picker already allows you to format date as .ShortTime as well as .ShortTime24. Which makes no sense.. each date is defaulted at 12:00AM or 0:00. Just a tease.   Stuck using a series of dropdowns at the moment 😕 Functional but not as pretty. ... View more

Currently the a ction  Send an HTTP request to Azure DevOps  supports a limited set of scopes  that do NOT include the scope vso.wiki, which is required to work with Azure DevOps Wikis.    Please add support for the scope vso.wiki to the Azure DevOps-connector, so that the action Send an HTTP request to Azure DevOps can be used to work with Wikis in Azure DevOps. ... View more

According to the Power Apps delegable functions and operations for SharePoint document, many functions and data types are delegable for SharePoint, but that's not the case for SharePoint calendars.  This limitation is not noted in the document.  Since SharePoint calendars are just another SharePoint list, I assume this to be a bug with the Power App connector.   This bug is easily recreated.  Connect a Power App gallery to a SharePoint calendar and use this formula for the Items source: Filter('SharePointCalendar', EventDate >= Date(2021, 8, 1)).  You will get the Delegation Warning and 500/2000 record limit.  This same formula works fine on a DateTime column is a standard SharePoint list.   Please fix!  Thanks ... View more

Can we get a detached version of the collections and variables? Just like we have the monitor? Today we can via clicking collections see what value we have in them, can we also get this as a detached version in a separate screen? In the picture below I added a suggestion button on how to access the collections/variables just like the 'Monitor' work today     ... View more

Allow change to default Font, Size, Color settings by exposing them in the App Properties setting list along with other startup properties. It is not sustainable to have to manually change design properties for every field on every form (font, size, color).    Please expose these settings on the App Screen (in Treeview), as configurable properties along with ConfirmExit, MinScreenHeight, OnStartup, etc... Ideally, create components them referencing these components (Size is App.DisplayFormSize instead of  hardcoding a value)  But even if they could be created out of the gate with my default values it would save a lot of time. The values I want to be able to control are: DisplayForm Font DisplayForm Size DisplayForm Label Width   (I don't always need it taking up 40% of my screen)  DisplayForm Text Color DisplayForm Font DisplayForm Fill Color DisplayForm DataCard Height -- The same list for EditForm -- Gallery Font Gallery Title 1 Size Gallery Title 2 Size  Gallery Title 3 Size Gallery Text Color Gallery Fill Color   If the holdup is not wanting to change the values within the application during the run, then don't allow it. I'd even settle for these values only being utilized at create time -- where the value on the card/field/gallery is still hard-coded, but it's hardcoded to MY default value set at create time.    It's hard to make the case this is more efficient/cheaper to use than a .NET development effort when a developer can do this with a simple stylesheet setting/change, and I spend HOURS painstakingly changing each field (and then changing it again when requirements change)   ... View more

Allow the storage of JSON in Dataverse/Dataverse for teams. Include:   Validation - confirm JSON format (obviously I can store this as basic text at present) Structural analysis (?) - suggest RDB schema based on similarity of the object structure of each record Inline editor/formatter (for grid view - some way to easily amend code) In-app performance warnings Documentation and use cases - e.g. my case is modelling regular entities (orders, claims) but want to include high-dimensionality entities in a flexible format that is still structured (can parse easily to use in an app) Understood there may be storage/performance issues with this (last points above), however IMO some things are better viewed/ported around as an object.   If I have not researched enough and this is already a suggested feature, apologies - I obviously did not see it come up in the "suggested" suggestions 🙂 ... View more

Would it be possible to have not just revision history, but versions of canvas apps, like DEV, SIT, UAT and PROD? For example when making a new app, we get the option to use full development options. So I can make my app in Dev mode, then when ready I can promote to SIT, UAT, but keeping the Dev one intact, then once testing is done, we can promote to PROD, where it is published to live etc. I know we have Save / Publish, but thats largely a Dev / live thing and I have to go live in order to give to testing. Also I know that I can create separate apps, i.e. App - DEV, App - SIT etc, but promoting the apps and updating them is a pain with the current tools. It would also be nice if we could prevent changes in Live until it has gone through the stages of SIT and UAT. It could even be one stage called testing, but ultimately, I would hope to get 3 links, one for SIT, UAT and PROD, but they all come from one app with the 4 versions. I hope that makes sense, I even have some ideas on what it could look like! ... View more

I use PowerApps to quickly prototype solutions. Boom, there said it. During RAD MS Teams call sessions I will mock up a working prototype application. During this time I capture Requirements, Stories, etc. in Label fields on the screens.    I would like a new Product Feature of PowerApps Canvas Design to Capture functional Requirements - and optionally link or create a New PBI or Item in Azure Dev Ops.   Requirements Capture (In Canvas Design) New in PowerApps is the ability to Capture Business and Technical Requirements. PowerApps can be used as a Rapid Application Development environment or Prototyping Tool that quickly enables citizen developers to capture requirements right on screen. This enables user design sessions both a visualization of what can be done and requirements document simultaneously.  Features Optionally - Configure your PowerApp to link to a specified project in Azure Dev Ops. (Configuration found on File Settings Blade in PowerApps. Once linked to ADO Project - Create Features, Stories, Tasks (or other Items) from within your requirement on the PowerApps Screen Designers can quickly create Rich Annotations and Text that are automatically numbered and visible on screen during design. Requirements are always hidden during Run time Requirements can be (toggled) hidden or shown during design with checkmark in the new Tab called requirements.  You can Pin a Requirement on Screen in Design or hide it however the Requirement will always be visible in the list of Requirements in new Requirements Tab next to [Screens Components Requirements] bold item is new in this release A complete list of All requirements Grouped by Screen in tree view appear within the Requirements new tab You can optionally download the requirements as a CSV file or XLSX file. ... View more

I often use the HTML text element to display custom tables of content, having the ability to manipulate the positioning with the "sticky" CSS tag would be huge!   ... View more

It would be great to have a simple way to get the Owner and Co-owners of a Power App As example it would be useful to have emails in order to report bugs or suggestions from the app ... View more