Our application is deployed by an installer which calls our VB.NET "scriptlets" that get compiled and used the SSRS Web Services to publish our reports. We have reports which have string parameters which allow nullable values and have the default value property set to [Null]. When a client comes along and modifies this report in Report Builder and accidently removes the Nulls Allow functionality and redeployed, then went back and corrected it to add back in the Allow Nulls with the default value of Null and redeployed again. The report didn't work when we called it unless this filter criteria was provided. What appears to be happening is the when Report Builder saves the report back to the server it's not properly setting the "Has Default" checkbox. Is there any way to force this to get set through Report Builder?
↧