Unanswered

Dataflows change import method from "merge" to "Append" after first run.

(1) Share

Report

Posted on by Kasper_L

Hi,

I have an issue to merge queries in the new dataflow setup. When I create the dataflow I want the data flow to "Merge" data into the destination table (dataverse). This is working in the first run, but when the dataflow should run again. it changed the settings to "Append" mode.

This is the setting when creating the dataflow,

After the first run the dataflow change the settings to "Append",

Is this a bug in dataflow? Or is their some settings I'm not aware of? I just want the dataflow to update a row if the row exist, and create a new row if the row do not exist.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (2)

All responses (9)

Answers (0)

SN-17101705-0 7 on at

Like (0)

Report

After you create and publish the dataflow for the first time, the option is automatically blocked. In order to change the option, you should create another dataflow or edit the existing one and click on "reset load settings".

If you select the option 'merge' and an error occurs after publishing, the option will be disabled, and 'append' will be selected as the default.

Was this reply helpful? Yes No
Kasper_L 12 on at

Like (0)

Report

Hi,

I do not have any errors when publishing my dataflow. And the strange part is that even the load settings says it is in append mode the dataflow is actual loading in merge mode. It seems to be a bug in the visual that shows it is append mode but actually behave as merge mode.

Just strange if I'm the only one experince this. I have also tested it with my colleagues, with exact same result.

Was this reply helpful? Yes No
IA-06112154-0 2 on at

Like (0)

Report

I'm also experiencing this exact issue. Did you manage to find a solution for this?

My Dataflow is setup to get data from an excel file in SharePoint with some minor transformations applied (remove some columns and change column format). The first import is fine but subsequent refresh switches to 'Append'. I have tried the 'Reset load settings' button but just ends up with the same result again.

Was this reply helpful? Yes No
CU13110418-0 2 on at

Like (0)

Report

...

Was this reply helpful? Yes No
Kasper_L 12 on at

Like (1)

Report

Hi IA-06112154-0

I currently have an support ticket with Microsoft. But so far all their attempt to help me is that they think I'm doing something wrong. But I think it is a bug in the system.

Are you sure that the dataflow is not merging data? even that the settings says appending?

I have tested it more and found out that the behavior of the dataflow. The flow is NOT appeding but it is actually merging. If you look at the settings the dataflows says pending. But if you then go to the coloumn mapping, the unique row is represent (In my case the row where I have mapped GUID). If I run the dataflow the dataflow is merging my data and not appending.

My theory is that this case in only a bug in the userinterface that is showing the wrong importmethod.

1 people found this reply helpful.

Was this reply helpful? Yes No
JanShhhh 4 on at

Like (0)

Report

We have been experiencing the same for a while now.

It is only a visual bug though. Merge Dataflows are showing as Append Dataflows aswell.

You can tell them apart, if a flow has a primary key in the column mapping settings, it is a Merge Dataflow, if it does not have one, it is Append.

1 people found this reply helpful.

Was this reply helpful? Yes No
SamuelBenjamin 70 on at

Like (0)

Report

Same here, I aggree it may be just a visual bug, as far as the dataflow is still merging data.

Also something weird is checking the refresh history, as far as it shows rows created, updatetd and failed. Updated rows will contain both modified and deleted. Makes no sense at all, should be fint to know how many rows has been added, modified and deleted, so you can easily double check the merge is working.

Was this reply helpful? Yes No
fingle 2 on at

Like (0)

Report

Hello. Is this any response or follow up to this issue please?

I'm concerned I'm using this feature in a production environment, and there is no support or resolution. Thanks.

Was this reply helpful? Yes No
KJ-14100940-0 2 on at

Like (0)

Report

I am also still experiencing this (have noticed this also a few years ago), and somehow it is ignoring the (composite) unique key to update existing records, while that's the whole purpose of "merging" instead of trying to insert duplicates...
The first run works fine, but at next runs it goes berserk on the "duplicates"...

Was this reply helpful? Yes No