You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ExtensionSettings=New-Object"$Namespace.ExtensionSettings"-Property @{ Extension="Report Server $DeliveryMethod"; ParameterValues=$ParameterValues }
303
+
$ExtensionSettings=New-Object"$Namespace.ExtensionSettings"-Property @{ Extension="Report Server $DeliveryMethod"; ParameterValues=$ExtensionParameterValues }
298
304
299
305
$MatchData=$Schedule
300
-
$ReportParameters=$Null
306
+
307
+
# Transform $Parameters to $ParameterValues
308
+
if ($Parameters-ne$null)
309
+
{
310
+
$parametersCopy=@{};
311
+
# First, remove null-valued keys - At some point between SQL Server 2005 and 2016 (probably 2012), null-valued keys are no longer stored in the database.
312
+
# null-valued keys are now represented in the SOAP API by not passing in the null-valued parameter.
313
+
foreach ($keyin$Parameters.Keys)
314
+
{
315
+
if ($Parameters[$key] -ne$null)
316
+
{
317
+
$parametersCopy.Add($key,$Parameters[$key]);
318
+
}
319
+
}
320
+
321
+
$Parameters=$parametersCopy;
322
+
323
+
# Similarly, if we pass in an empty collection, the SOAP API will also be unhappy!
0 commit comments