Hallo,   currently it is not possible to block specific connectors for Dataflows, i.e. DLP policies can not be used to prevent a user from importing data from e.g. a Web API into CDS (if that user has appropriate permissions to write data into the CDS), even if a DLP policy is blocking the HTTP connectors for Power Automate Flows.   DLP policies should be applicable for dataflows in the same way that they are applicable for Power Automate Flows. ... 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

When you add a flow connector to an app and afterwards the flow parameters are changed, this change is not present in powerapp. You have to delete the connection and to add it again. Why is there a difference to connections to SharePoint lists, which you can update just by clicking Refresh at the conncector sub menu? Please add the refresh option for Flow connectors ... 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

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

Please make the paid component of Gateways either free for use in Flows, or make it CLEAR that it is a PREMIUM connector at the beginning.   Some connectors in Power Automate Flows are branded PREMIUM, but the File System connector is not. I have an Office 365 Business Premium license, so assumed I would be able to use the File System Connector. The purpose of this connector is to manipulate on-premises files and folders within a Flow.   What is not clear to users is that they require a standalone license to use a separate prerequisite Gateway on their local system, otherwise the connector cannot be saved.  Users can build their entire flow, download and install their Gateway, change their Region in the Gateway to match the Power Apps region so it is recognised... And only at the very last step are they informed of this paid requirement, when entering the Gateway - whereupon Flow kindly states that their license does not include use of Gateways.   Please make the paid component of Gateways either free for use in Flows, or make it CLEAR that it is a PREMIUM connector at the beginning. ... View more

In French, we use apostrophes. Entering a value with apostrophe in the "Filter Query" generates an error in power automate. Best Regards. ... View more

There is a new Collumn type "Location" in SharePoint. This Type is currenly not fully supportet in PowerApps. The Collumn isn't Editable in the DataCards. Yet this is a common need for Solutions in Logistics. Thank you in advance. ... View more

It would be great if we were able to set Status and Status Reason on the records for an entity in the CDS with a Power Platform Dataflow with CDS as destination. ... View more

i have dataflows attached to my entities in order to update data from various sources. It would be amazing if i could add a dataflow to my solution so that i could migrate it to a different environment. Along with all the other stuff in my solutions. ... 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

Super idea :   One should be able to create a trigger on a SQL on-Prem server. And then PowerApps should be able to update the column in the target table without getting any "The requested operation is invalid. Server Response : Microsoft SQL :The target table XXX of the DML statement can not have any enabled triggers if the statement contains an OUTPUT clause without INTO clause."   Any flow workaround won't work because on prem. Or else, just tell me (I wish i were wrong so bad !) 😉 ... 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

It is really great that you can choose to create an entity and fields when mapping between source and destination in a Power Platform Dataflow. But there is no way to control which prefix the new entity gets as well as the prefix for the fields created.    Would be so much better if we were able to create Power Platform Dataflows from within a Solution and if the created entity and the fields then got the prefix from the Publisher related to the Solution. ... View more

Add the CDS connector to DataFlows in make.powerappscom   Why can Customer Insights connecto to CDS, but DataFlows can't?    ... View more

I would like to see a PowerApp run as an Azure Managed Service Identity.  This would allow for the PowerApp connect to sources and destinations as the MSI vs. AAD user. ... View more

Hello,   I suggest to add the option of Incremental Refresh in Dataflows for Power Apps, in the same way Power BI has it. Most of loaded information has the historical data+new data which delays a lot the loading of a whole report. Would that be possible?   Thanks ... View more

There are severe limitations to the data integration legacy app (make.powerapps.com) when it comes to monitoring refresh jobs for integration projects.    Currently, there is no way to get notifications about failed jobs. In addition, there is no warning mechanism that triggers an email to admins when a DI project stops running, but no error is thrown (this is also missing in the new experience). The latter has happened for one of our clients on more than one occasion.   As the data integration legacy app will not receive any more investments from Microsoft, I would like to have the ability to migrate our current integration projects to the new data integration portal (admin.powerapps.com). This way we can leverage the notifications feature which is available on the new portal for scheduled sync.    Is this on your roadmap and if so when is it planned to offer migration between the two portals?   ... View more