Forum Discussion

BrendanOne51's avatar
BrendanOne51
New Member
10 months ago

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...
cicd
svenchio's avatar
svenchio
Icon for Super User rankSuper User
10 months ago

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  

 

 

 

  • BrendanOne51's avatar
    BrendanOne51
    New Member
    10 months ago

    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's avatar
      svenchio
      Icon for Super User rankSuper User
      10 months ago

      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