Unable to suppress warning message and capture the message in a variable

[pshum777]

Verified issue does not already exist?

No, I did not search

What error did you receive?

Attempt to capture warning from Get-DbaNetworkCertificate and suppress the display

as described in this article: https://nocolumnname.blog/2019/06/28/hiding-warnings-in-dbatools/

Steps to Reproduce

$WarningToDo = @{
WarningAction = 'SilentlyContinue'
WarningVariable = 'RestoreWarning'
}

Get-DbaNetworkCertificate -SqlInstance sqldb1211.shoebox56.org @WarningToDo
$RestoreWarning

Please confirm that you are running the most recent version of dbatools

Get-InstalledModule -Name dbatools

Version Name Repository Description

---

2.1.27 dbatools PSGallery The community module that enables SQL Server Pros to automate database development and server administration

Other details or mentions

No response

What PowerShell host was used when producing this error

Windows PowerShell ISE (powershell_ise.exe)

PowerShell Host Version

Name Value

---

PSVersion 5.1.19041.5737
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.19041.5737
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

SQL Server Edition and Build number

sql server 2019 EE CU 29

.NET Framework Version

.NET Framework 4.8.9300.0

[andreasjordan]

That one is easy to explain. Have a look at the source code. The command just uses another command and filters the output.

Your special parameters are not forwarded to that command.

You should use the other command directly.

[pshum777]

Yes, I was able to use the underlying dbatools cmdlet. It seems to be inconsistent in behavior among the cmdlets and would appreciate if the doc can point that out. [Icon Description automatically generated] Peter Shum Principal Database Administrator 541.681.6373 (direct) 541.513.2195 (mobile) From: Andreas Jordan ***@***.***> Sent: Saturday, May 3, 2025 1:06 AM To: dataplat/dbatools ***@***.***> Cc: Peter Shum ***@***.***>; Author ***@***.***> Subject: [EXTERNAL] Re: [dataplat/dbatools] Unable to suppress warning message and capture the message in a variable (Issue #9658) Caution: This email originated outside of OCCU. DO NOT CLICK links or attachments unless you know the sender and trust the content is safe. [Image removed by sender.]andreasjordan left a comment (dataplat/dbatools#9658)<#9658 (comment)> That one is easy to explain. Have a look at the source code. The command just uses another command and filters the output. Your special parameters are not forwarded to that command. You should use the other command directly. - Reply to this email directly, view it on GitHub<#9658 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BSC4MSJILJQCAEMDTHAR7U324R2E3AVCNFSM6AAAAAB4K6SH36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNBYGQ4TQMJTGM>. You are receiving this because you authored the thread.Message ID: ***@***.***> Confidentiality notice: This e-mail may contain confidential information and is for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and delete the e-mail and any attachments from your device. Personal e-mails are restricted by OCCU policy. OCCU specifically disclaims any responsibility or liability for any personal information, or opinions of the author, expressed in this e-mail. Although OCCU takes reasonable precautions to ensure no viruses are present in e-mail, it will not be liable for any loss or damage arising from the use of this e-mail or attachments.

[andreasjordan]

I was able to reproduce the problem. And I was wrong. There is no need to pass the common parameters to the next level:

function Test-CommonParametersInner {
    [CmdletBinding()]
    param ([string]$TestValue)
    Write-Warning -Message "TestValue: $TestValue"
}

function Test-CommonParametersOuter {
    [CmdletBinding()]
    param ([string]$TestValue)
    Test-CommonParametersInner -TestValue $TestValue
}

Test-CommonParametersOuter -TestValue MyTest -WarningAction SilentlyContinue -WarningVariable warn
$warn

But we don't use Write-Warning but a custom command Write-Message. Maybe this command makes the difference.

@FriedrichWeinmann Maybe you can help?