Share your ideas and vote for future features

The key fields of the entity are displayed when mapping from an external data source to the fields of an existing entity in the CDS using the data flow. However, multiple keys are registered in the entity but cannot be selected. Please improve the function so that you can select any registered key. ... 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

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

currently it is possible to map source columns in the Field mapping of dataflows to fields of a 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

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

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

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

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

When you have a dataflow that has a lot of queries, the page where you select which queries to load data to CDS has the (list of) queries on the left, and once you click on a query, that query's load settings on the rest (right side) of the page. The two should not scroll together, it makes working with dataflows that have lots of queries a nightmare. Please make it so the list of queries scrolls independently. ... View more

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

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

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

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

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

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

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

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