Share your ideas and vote for future features

While the PowerShell-module "MicrosoftPowerBIMgmt.Data" contains cmdlets for the management of dataflow ( Get-PowerBIDataflow, Export-PowerBiDataflow), the PowerShell-modules for the Power Platform  ("Microsoft.PowerApps.Administration.PowerShell" / " Microsoft.PowerApps.PowerShell")  do not contain any cmdlet that allows the managemet of dataflows.   Please add PowerShell-cmdlets to the PowerShell-modules for the Power Platform, that allow the management of dataflows in the Power Platform, e.g.  Get-AdminPowerAppDataflow. ... View more

Would be very handy to have the ability to trigger Dataverse Dataflow from Power Automate. Sometimes the Dataflow refresh/scheduled run  do not satisfy the requirements and the trigger needs to run based on some business logic such as when a file is uploaded or when an event occurs in the system.   ... View more

When running a DataFlow, it should be possible to select the Application User for "run as". The normal users in Dynamics don't have enough API's pr 24 hours.      While the application user has 100,000 SSIS integrations with KingsWaySoft can do Application User, and would by that be more logical to choose for a larger scale deployment, even though I would prefer to user DataFlow because of simplicity 🙂 ... View more

Hi lovely community,   especially when building dataflows, theres always the case to cancel them (e.g. if you know that a dataflow will probably take more than 2 hours). Of course I know to preparing Dataflows via Power Query in Power Bi or Excel, but of course I wanna see the result of my query in Dataflow especially for some mystery error messages in Excel refresh protocol...:)   It would be great to be able to intervene here as a user in order to be able to cancel the dataflow.   BR, Sven ... View more

Currently, Power App Dataflow works fine while loading lookup columns by defining a single column Alternate Key. However, if we add multiple fields/columns in a single Alternate Key, Dataflows does not support it. Please add this functionality.   Refer below scenario for reference -  https://powerusers.microsoft.com/t5/Power-Platform-Integrations/Dataflow-errors-with-Alternate-Keys-of-multiple-columns/td-p/756177   ... View more

Documentation states the following limitation:    Using gateways in dataflows is only supported for people with  Admins  permissions.  Can use  and  Can use + share  permissions levels are not currently supported.   Please lift this limitation because it basically kills every ambition to move data into CDS when there are more than an handful of users in the company. ... View more

Power Apps Dataflows needs to support upsert (insert and/or update). Currently Dataflows only supports insert/create and delete operations (if enabled). This means that every time a Dataflow is ran will insert duplicate records. If an alternate key is defined then those records will fail during the run because of duplicate key. If delete records is enabled, then all records will be deleted and created per run. There are several keys issues with this: Upon delete, all history and auditing history are lost Harder to determine records that changed after a Dataflow run. Modified On will always be the Created On  Unnecessary triggers (i.e. plugins, flows, workflows, etc) could be invoked upon create and/or delete Performance: additional redundant delete and create transactions are executed when nothing changed ... View more

Dataflows is such a nice addition to loading data into CDS and Azure data lake. However, there is a limitation of importing 6000 records per 300 seconds. Users get below error when exceeding the limit.   Number of requests exceeded the limit of 6000, measured over time window of 300 seconds.   The above limit may sound reasonable for third party API integrations but not suitable for dataflows which deal with importing large chunks of data. Since dataflow is an inherent feature of the product, there should not be any throttling limits in the first place. As there is no source code available to tweak, we neither control exceptions nor delay the execution as per the API limits.   Please upvote and let's see what Microsoft has to say about it. ... View more

currently it is possible to map source columns in the Field mapping of dataflows to fields of a dataverse-table (aka CDS-entity) with data-type Text, Date,  Floating Point Number, etc- but it is not possible to map to fields of data-type Lookup. Please add support for fields of data-type Lookup to the Field mapping of dataflows. ... View more

Hi,   We have an app that uses a Flow with the SAP ERP (preview) connector to get and post data to our SAP systems. The issue we are facing is that when a user will use the app for the first time they will see the standard prompt to add their credentials so that the SAP connector can use these (see example1 and example2).   This is fine however if the user accidently inputs the incorrect username or password at this point there is no prompt to advise that their credentials are incorrect. Instead the box disappears and loads the app like normal and you will not know that the credentials are incorrect until the app tries to call the Flow to connect to SAP. At this point the SAP ERP connector in the Flow will retry 4 times and then fail due to the credentials being incorrect.   That is part 1 of our problem. The next part is when the user then goes to open the app again and change their credentials to the correct ones, there is no way to get the boxes shown in Example 1 & Example 2 back again meaning the incorrect credentials are stored and cannot be changed even if you wanted to.   This is causing many issues for us as every user at some point will put an incorrect password/username in and we have a number of security policies in place around our SAP password meaning that ever month you are forced to change your password. When you change your SAP password you cannot then change your credentials stored in the PowerApp to your new credentials.   This is a massive limitation currently and one that is preventing us as a company from using PowerApps to connect and use SAP.   Can this be resolved at all?   Thanks.   ... View more

Currently we need to manually refresh a dataflow or set it for a scheduled refresh.   However, it would be great if we can do so via a Rest API. By that we can programatically make an HTTP post request to invoke the API for the dataflow refresh   The similar functionality is available for Power BI dataflows : https://docs.microsoft.com/en-us/rest/api/power-bi/dataflows/refreshdataflow   It would be great to have the same feature for Power Apps dataflows as well.   Thanks, Raj ... View more

This can only be done from the Data Integration section, tab Scheduling, of the admin page, but not directly from Power Apps. Moreover, even if you turn on email notification for a dataflow from the admin page, if you edit the dataflow's refresh settings from Power Apps, the notification is turned off. Can we please have this directly in Power Apps, when editing a dataflow? ... View more

Hi!   Like already asked for here: https://powerusers.microsoft.com/t5/Common-Data-Service-for-Apps/Dataflows-Authentication-using-API-Key-or-OAuth-2-0/m-p/568602#M5297 I would like to be able to push some big data via Rest API (json) into my Common Data Service. I'm already able to do that with Power Automate, but here I just can do it for each record via slowly "Apply to each" loop (think about running time with over 10000 records..) and without nice Power Query options.   So I can image there some different options:   - Power Automate Flow: Flexible triggered REST APi with "Upload JSON records" CDS Action incl. Power Query ETF process - Dataflow Web API with API Key / OAUTH2.0 Authentification - Dataflow Custom Connection Option   BR, Sven ... View more

Currently a CDS Dataflow can have only one owner - the person who created the dataflow. If you use this technique to get data into CDS on a schedule you want to be able to share the ownership with multiple people, like you do with Apps and Flows.    Please add the ability to share ownership. Please add the ability for environment admins to see all Dataflows in their environment. ... View more

As of now, Azure CosmosDb Connector is available for logic apps and Flow services. So while building PowerApps with Azure Cosmos DB as the backend will have to write Flow/logic apps and then call that Flow in PowerApps. Wish could avoid writing flows for all transactions that could be done on PowerApps if Azure Cosmos DB Connector is supported for PowerApps as well!   Thanks. ... View more

As per my query I would suggest the ability to link new contact Entity records to existing Account Entity records during a dataflow import.   I understand that this can be accomplished via a manual import from Data Management in the PowerApps Admin Center, however this lacks the Transform and schedule functionality of dataflows. ... View more

Need the ability to map Lookup type of fields directly in the Field Mapping screen in Dataflows. The only workarounds found are the following:  Set up some  Alternate Keys  on entities Single Line of Text field and populate the source value. On create/update, set the lookup field based on that text value with Power Automate or Plugin If need to set default values, require a sync Plugin on Pre-Operation to set the values ... View more

A dataflow usually contains multiple queries, and the results of a few of these queries get loaded into entities. This works fine most of the time. The problem is when one of these queries fails. My expectation is that when this happens, none of the queries will load their result into CDS. However, this is not the case.   Currently all the queries but the failing one will load data into CDS. This makes little sense, see some examples below. Please make the dataflow atomic (transaction), so that either every query designated to load data in CDS does so, either none does. Maybe even add a setting to toggle this atomic/transaction behavior on/off for each dataflow.   Example 1: In a dataflow with 4 queries where 1 query is for a parent entity and the other 3 are for child entities. Why load the children into CDS if the parent could not be loaded?   Example 2: I am loading data from JSON files. To avoid my dataflow getting slower and slower as files pile up, I keep track of the files I processed (loaded data from) and will not process them again. I have a ProcessedFiles entity in CDS where I store the list of files. One of the queries at the beginning of the dataflow will filter out from the input files the ones I already processed, then subsequent queries will only load data from the new files. Finally the dataflow loads new entities to CDS for both the data loaded and the files I loaded them from. However, if the query that loads the data from the files fails, the query that writes the new files to the ProcessedFiles entity still executes.  ... View more

OAuth 2.0 Resource Owner Password Credentials (ROPC), also known in Postman as the 'Password Credentials' OAuth 2.0 Grant Type. See here for more information: https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth-ropc The current allowed method from the Generic OAuth 2.0 - Generic Oauth 2 Identity Provider only allows for: Client id & Client secret. This does not grant access to OAuth 2.0 APIs that use a 'Password Credentials' method, using 'Username' and 'Password' This is a necessary feature addition to Custom Connectors enable developers to use API authentication that have expiration on their bearer tokens, and can only be logged in via Username and Password.   Original Thread: https://powerusers.microsoft.com/t5/Building-Power-Apps/OAuth-2-0-Resource-Owner-Password-Credentials-on-Custom/m-p/490451 ... View more