SQL [DBNULL] datatype breaks calling runbooks
When a runbook uses sqlcmd and returns a dataset, and that dataset has a [DBNULL] data type (A column IS NULL in the sql return), the calling runbook errors out.
2 runbooks. One runs in azure, another runs on Hybrid worker. The azure runbook starts the Hybrid worker runbook. The hybrid worker runbook does a SQL query using invoke-sqlcmd. The SQL query returns a dataset which has a NULL value in one of the columns. That return is then sent to the calling runbook in Azure.
I forget the failure, but it appears JSON can't format it correctly.
NULL should be represented in JSON.
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature