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
V-yubandi-msft's avatar
V-yubandi-msft
Icon for Community Support rankCommunity Support
10 months ago

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.