Forum Discussion
Deployment pipeline issue
I am deploying a pipeline item which contains a lookup activty which executes a stored procedure. The stored procedure takes parameters. One of the parameters needs to be treated as null.
When deploying using the Fabric Deployment Pipeline this 'Treat as Null' setting becomes unchecked. The schema compare does not highlight the difference either. Is this a bug or is there some way around this?
6 Replies
- svenchio
Super User
Hi BrendanOne51 I tried to replicate your issue but I wasn't able to do so, you did not mentioned if your workspace was git-enabled or not nor the web browser you're using, in my case, I'm using MSFT EDGE browser and I ALWAYS have my sandbox workspace git-enabled because I wanted to see if the item properties being track, in this case as show below, the Treat as Null is tracked
Then I proceed to create a deployment pipeline (legacy) and deployed the pipeline and sure it created a data factory pipeline/stored procedure task correctly .
I then changed uncheck the Treat as null as sure the change was picked by the pipeline!
Conclusion: I could not re-create your issue and from my perspective, everyhing is working as expected, NO BUGS under the conditions I explained (workspace git-enabled and legacy deployment pipeline)
My suspicious is that you MISSED TO SAVE YOUR CHANGES on the data factory pipeline, unlike notebooks that auto-saved themselves, data factory pipeline's changes HAS TO BE SAVED manually (see save button on image below)
I suggest you to try again, connect your workspace to git, do a change AND SAVE, and from Deployment pipeline, see if the change gets reflected... most likely it will, but ping if otherwise.
If you find this information useful, I would appreciate a kudos and if my recommendatios are accurate and correct, mark as solution so others facing the same, find answers more quickly. All the best
Thanks for the detailed response. The source pipeline in the dev workspace is definitely saved. I also have my dev workspace synced with git but I can't see a 'value' in the pipeline-content.json file for the parameter that I am setting as null. In your example above it is coming through as null.
When I view in the code editor it is showing correctly
From what I can tell this happens only when using a native Fabric SQL Database connection. Using a SQL connection for a Fabric SQL Database works fine. So it appears this is a bug with the Fabric SQL Database Connection in the Pipeline and not an issue with the deployment pipeline.
- svenchio
BrendanOne51 I'm using a SQL Connection, I don't think the connection is the issue, I think is more the UI/Browser, just for the sake of curiosity, what browser are you using? Did you repeat the test using EDGE browser?
Let me know -🤞 ... all the best
mikeburekAdvocate III
I had something like this happen to me with the Copy activity on the "delete file after copy" option getting unchecked when deploying from my test to prod. Though it worked right for dev to test.
V-yubandi-msftCommunity Support
Hi BrendanOne51 ,
This issue does not seem to be related to saving, Git, or the browser. The main difference is the type of connection used in the pipeline. When a stored procedure parameter is set to Treat as null
1. If you use a native Fabric SQL Database connection, this setting isn’t recorded in pipeline content.json (there’s no "value": null entry), so Deployment Pipelines and Schema Compare can’t detect or keep the value.
2. If you use a standard SQL connection with the same Fabric SQL Database, the value null entry is included properly, and deployment works as expected.
This suggests the behavior is specific to the native Fabric SQL Database connector, not Deployment Pipelines or Git. For now, using a standard SQL connection is a reliable workaround.
It’s also a good idea to submit a support ticket to Microsoft so their product team can look into the issue.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thanks.
- V-yubandi-msft
Hi BrendanOne51 ,
Could you let us know if your issue has been resolved? If you’ve received any updates or advice from the Microsoft team, please share them here so others with the same problem can benefit.
Thank you.
