Supplies are limited. Contact info@espc.tech right away to save your spot before the conference sells out.
Get your discountScore big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount
Hello,
I have a data pipeline in a workspace with DEV connection (to write in DEV warehouse) and I want to change the connection to write in UAT workspace.
I change with the UAT connection and save.
If I close the data pipeline and reopen it, the DEV connection is mapped again...
To change the connection, I have to delete the script component and create a new one...
Do you have the same problem?
Thank you in advance for your feedback,
Vivien
Solved! Go to Solution.
Hi @vivien57
It appears you are experiencing an issue with saving connection changes in a Microsoft Fabric data pipeline. This problem seems to be a known issue that Microsoft is currently working to address.
The behavior you’re describing matches a known issue documented by Microsoft:
When you edit a connection in a stored procedure or script activity within a data pipeline, the changes appear to save initially. However, after reloading the page, the connection reverts to its previous state.
As a workaround, Microsoft recommends deleting and recreating the stored procedure or script activity using the new data warehouse connection. This aligns with your observation that you need to delete the script component and create a new one to change the connection successfully.
if this is helpful, please give kudos and accept this as solution.
Thanks
Hi @vivien57
It appears you are experiencing an issue with saving connection changes in a Microsoft Fabric data pipeline. This problem seems to be a known issue that Microsoft is currently working to address.
The behavior you’re describing matches a known issue documented by Microsoft:
When you edit a connection in a stored procedure or script activity within a data pipeline, the changes appear to save initially. However, after reloading the page, the connection reverts to its previous state.
As a workaround, Microsoft recommends deleting and recreating the stored procedure or script activity using the new data warehouse connection. This aligns with your observation that you need to delete the script component and create a new one to change the connection successfully.
if this is helpful, please give kudos and accept this as solution.
Thanks