{"id":570,"date":"2021-12-07T06:36:37","date_gmt":"2021-12-07T14:36:37","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/powershell-community\/?p=570"},"modified":"2021-12-07T06:36:37","modified_gmt":"2021-12-07T14:36:37","slug":"how-to-use-psdefaultparametervalues","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell-community\/how-to-use-psdefaultparametervalues\/","title":{"rendered":"How to Use $PSDefaultParameterValues"},"content":{"rendered":"

Q:<\/strong> When I use cmdlets like Receive-Job<\/code> and Format-Table<\/code>, how do I change default values of the Keep<\/strong> and Wrap<\/strong> parameters?<\/p>\n

A:<\/strong> Use the $PSDefaultValues<\/code> automatic variable.<\/p>\n

When I first discovered PowerShell’s background jobs feature, I would use Receive-Job<\/code> to view job output – only to discover it’s no longer there. And almost too often to count, I pipe objects to Format-Table<\/code> cmdlet only to get truncated output because I forgot to use -Wrap<\/code>. I’m sure you all have parameters whose default value you would gladly change – at least for your environment.<\/p>\n

I’m sure you have seen this (and know how to use Wrap<\/strong>), like this:<\/p>\n

PS> # Default output in a narrow terminal window.\nPS> Get-Service | Format-Table -Property Name, Status, Description\n\nName              Status Description\n----              ------ -----------\nAarSvc_f88db     Running Runtime for activating conversational \u2026\nAJRouter         Stopped Routes AllJoyn messages for the local \u2026\nALG              Stopped Provides support for 3rd party protoco\u2026\nAppHostSvc       Running Provides administrative services for I\u2026\n...\nPS > # Versus this using -Wrap\nPS > Get-Service | Format-Table -Property Name, Status, Description -Wrap\n\nName             Status Description\n----             ------ -----------\nAarSvc_f88db    Running Runtime for activating conversational agent\n                        applications\nAJRouter        Stopped Routes AllJoyn messages for the local\n                        AllJoyn clients. If this service is stopped\n                        the AllJoyn clients that do not have their\n                        own bundled routers will be unable to run.\nALG             Stopped Provides support for 3rd party protocol\n                        plug-ins for Internet Connection Sharing\nAppHostSvc      Running Provides administrative services for IIS,\n                        for example configuration history and\n                        Application Pool account mapping. If this\n                        service is stopped, configuration history\n                        and locking down files or directories with\n                        Application Pool specific Access Control\n                        Entries will not work.\n<\/code><\/pre>\n
So, the question is: how to tell PowerShell to always use -Wrap<\/code> when using Format-Table<\/code> or Format-List<\/code>? It turns out there is a very simple way: use the $PSDefaultParameters<\/code> automatic variable.<\/p>\n
The $PSDefaultParameters<\/code> automatic variable<\/h2>\n
When PowerShell (and Windows PowerShell) starts, it creates the $PSDefaultParameters<\/code> automatic variable. The variable has a type: System.Management.Automation.DefaultParameterDictionary<\/strong>. In other words, the variable is a Powershell hash table. By default, the variable is empty when you start PowerShell.<\/p>\n
Each entry in this hash table defines a cmdlet, a parameter and a default value for that parameter. The hash table key is the name of the cmdlet, followed by a colon (:<\/code>), and then the name of the parameter. The hash table value for this key is the new default value for the parameter.<\/p>\n
If you wanted, for example, to always use -Wrap<\/strong> for the Format-*<\/code> cmdlets, you could do this:<\/p>\n
$PSDefaultParameterValues.Add('Format-*:Wrap', $True)<\/code><\/pre>\n
Persist the change in your profile<\/h2>\n
Any change you make to the $PSDefaultParameterValues<\/code> variable is only applicable for the current session. And the variable is subject to normal scoping rules – so changing the value in a script does not affect the session as a whole. That means that if you want these changes to occur every time you start a PowerShell console, then you add the appropriate statements in your profile.<\/p>\n
On my development box, I use the following snippet inside my $PROFILE<\/code> script:<\/p>\n
$PSDefaultParameterValues.Add('Format-*:AutoSize', $true)\n$PSDefaultParameterValues.Add('Format-*:Wrap', $true)\n$PSDefaultParameterValues.Add('Receive-Job:Keep', $true)<\/code><\/pre>\n
Summary<\/h2>\n
The $PSDefaultParameterValues<\/code> automatic variable is a great tool to help you specify specific values for cmdlet parameters. You can specify one or more cmdlets by using wild cards in the hash table’s key. Remember that the hash table key is the name of the cmdlet(s), a colon, and then the parameter’s name. Also, the hash table value is the new “default” value for that parameter (and for the specified cmdlet(s)).<\/p>\n
You can read more about $PSDefaultParameterValues<\/code>, and other preference variables in about_Preference_Variables<\/a>. And for more details of parameter default values, see the about_Parameters_Default_Values help file<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Q: When I use cmdlets like Receive-Job and Format-Table, how do I change default values of the Keep and Wrap parameters? A: Use the $PSDefaultValues automatic variable. When I first discovered PowerShell’s background jobs feature, I would use Receive-Job to view job output – only to discover it’s no longer there. And almost too often […]<\/p>\n","protected":false},"author":4034,"featured_media":77,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[13],"tags":[59,60],"class_list":["post-570","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell","tag-default-parameter-values","tag-parameters"],"acf":[],"blog_post_summary":"
Q: When I use cmdlets like Receive-Job and Format-Table, how do I change default values of the Keep and Wrap parameters? A: Use the $PSDefaultValues automatic variable. When I first discovered PowerShell’s background jobs feature, I would use Receive-Job to view job output – only to discover it’s no longer there. And almost too often […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/posts\/570","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/users\/4034"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/comments?post=570"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/posts\/570\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/media\/77"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/media?parent=570"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/categories?post=570"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/tags?post=570"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}