Share via

UI Error: Sink Dataset Parameters disappearing in Synapse Copy Activity

Diego Cazetta 0 Reputation points
2026-04-02T12:22:21.49+00:00

Hi,

I am experiencing a technical issue with the Azure Synapse Studio interface. When attempting to map a Pipeline Parameter to a Dataset Parameter within a Copy Activity, the UI fails to save the input.

Observed Behavior:

  1. I navigate to the Sink tab of a Copy Activity.

I see the defined Dataset properties (parameters).

I use the "Add dynamic content" link to assign a pipeline variable to the dataset parameter.

After clicking "OK", the entire "Dataset properties" section disappears from the panel.

After refreshing the view, the fields reappear but they are blank. The value is not persisted.

Technical Details:

Source: Web Activity Output

  • Sink: ADLS Gen2 (JSON)

I have attached screenshots of the UI state before and after the crash. Is this a known bug in the current Studio release, and is there a recommended browser or workaround for this?

User's imageUser's image

Azure Synapse Analytics
Azure Synapse Analytics

An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Smaran Thoomu 34,960 Reputation points Microsoft External Staff Moderator
    2026-04-03T07:55:51.4466667+00:00

    Hi @Diego Cazetta
    Thanks for sharing the details - this helps.

    What you’re seeing looks like a UI issue in Synapse Studio, not a problem with your pipeline logic. This behavior (values not persisting and section disappearing) has been seen in a few cases, especially when using dynamic content.

    What you can try

    • Refresh and re-enter once - Sometimes it doesn’t save on the first attempt but works after a refresh.
    • Switch browser / use InPrivate mode - Try Edge (recommended) or Chrome in Incognito - this often fixes UI caching issues.
    • Clear browser cache - Old cached scripts can cause this exact behavior.
    • Use Code view as workaround Go to “Code” view of the pipeline and manually add the parameter mapping - this bypasses the UI issue and usually works reliably.
    • Re-select dataset - Remove and reselect the sink dataset, then try adding the dynamic content again.

    This is most likely a portal/UI glitch, not a configuration issue. Using Code view or a different browser session is the quickest workaround.

    If it still doesn’t persist after trying the above, let me know - we can check the JSON together.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.