Splatting and mutually exclusive parameters

The idea

Splatting passes a collection of arguments to a command. Hashtable splatting names each parameter, making a larger call easier to inspect and allowing optional parameters to be assembled deliberately. The keys must be actual parameter names, and the values still pass through normal binding, conversion, and validation. A splat is structured argument data, not a string of PowerShell source to execute.

Parameter sets express different valid call shapes, such as choosing a record by identifier or by name. Put each exclusive mandatory parameter in its own set and handle the selected set explicitly through PSCmdlet.ParameterSetName. Supplying incompatible parameters should fail during binding rather than forcing a guess inside the function. Test each valid set, missing mandatory inputs, and the invalid combination of both modes.

function Get-RecordLabel {
    [CmdletBinding()]
    param(
        [Parameter(Mandatory, ParameterSetName='ById')][int]$Id,
        [Parameter(Mandatory, ParameterSetName='ByName')][string]$Name
    )
    if ($PSCmdlet.ParameterSetName -eq 'ById') { "id:$Id" }
    else { "name:$Name" }
}
$arguments = @{ Id = 7 }
Get-RecordLabel @arguments

id:7

The hashtable supplies the Id parameter, selecting ById. Binding establishes the valid input mode before the function body runs.