Upsert options not showing in Copy Acivity after initially creating pipeline. Settings are still in JSON?

Derek Horrall 196

I am not getting an error, but I think this might be UI bug? After initially creating Upsert and adding keys, those options no longer show up in UI. The settings are in the JSON, but not are not displayed in UI. Anybody else see this behavior? My sink is Azure Synapse Dedicated pool...

Json:

User's image

It should look like this (as it did when I created it):
User's image

MartinJaffer-MSFT 26,036 Reputation points

2023-03-25T00:09:07.6433333+00:00

@Derek Horrall Hello and welcome to Microsoft Q&A.

I understand you are encountering unexpected behaviour in the Copy Activity UI when the sink is Synapse dedicated?

. . .

I'm seeing it too now! I'm going to take a closer look.
MartinJaffer-MSFT 26,036 Reputation points

2023-03-25T00:25:43.9733333+00:00

@Derek Horrall

Okay I think I know where it has gone. I'm still testing the why. Notice the background color for the "Key Column" section is less white, a bit more grey, compared to the background color in "Dataset Properties"?

In the upper picture you shared, between "Copy method" and "Bulk Insert table lock", there is a grey bar. I believe it failed to expand.

I have an idea to test...
MartinJaffer-MSFT 26,036 Reputation points

2023-03-25T00:53:11.9433333+00:00

@Derek Horrall

I thought it might be about the parameterization causing the key column chooser to fail loading options. Doesn't seem to be the cause. I'm actually having difficulty getting it to display the Key Columns part in the first place. Next I'll test whether it is about schema.

Works fine in Synapse though. So far seems to be just Data Factory.

Hold on, why does "Bulk Insert table lock" and other bulk insert items stay the same when I click between Bulk Insert and Upsert. I don't think those are supposed to be there.

. . .

Okay, yeah this is worse than I thought, those Bulk Insert bits are misleading, as they don't affect changes to the JSON when Upsert is selected. Yeah its broken.

Thank you for bringing this to our attention. I'll let the developers know Monday. I'm glad you are comfortable with editing the JSON. Thus it is not an immediate blocker.