How to specify the number of decimal places in PowerShell Output

PowerShell does not have any number formatting built into it. For this reason, we have to use a little bit of .NET to make some changes. Let’s say you have the number 45.54321 and you only want to display the first 2 decimal places. Here is the code.

$Num = 45.54321

"{0:N2}" -f $Num

45.54

The first zero is an index number (You will see how this works in a minute.) The N tells us what type of data we are formatting. I Borrowed the below chart from this Microsoft article.

Name	Specifier	Description
Currency	C	The value is displayed as currency, using the precision specifier to indicate the number of decimal places to be displayed.
Decimal	D	The value is displayed using the number of digits in the precision specifier; if needed, leading zeroes are added to the beginning of the number.
Percentage	P	The value is multiplied by 100 and displayed as a percentage. The precision specifier indicates the number of decimal places to be displayed.
Hexadecimal	X	The value is displayed as a hexadecimal number. The precision specifier indicates the number of characters to be displayed, with leading

The number 2 tells us how many decimal places to use.

Let’s go back to that index number. Give this a try.

$Num = 45.54321, 36.75256, 65.34255

"{0:N2}","{1:N2}","{2:N2}" -f $Num

45.54 36.75 65.34

We can also format this information as currency.

$Num = 45.54321, 36.75256, 65.34255

"{0:C2}","{1:C2}","{2:C2}" -f $Num

$45.54 $36.75 $65.34

Comments

Unknown said…

Here is my problem. I'm trying to sum multiple $ amounts from into a singular total amount. The issue is the data I’m starting with has no decimal point. First 7 digits are dollars with left pad zero’s last 2 digits are cents. How would I sum these into a singular total with the original formatting?

Below are 6 different amounts using (7,2) format as each number
000000025 000001000 000283711 000025000 037000054 000000017
.25 + 10 + 2837.11 + 250 + 370000.54 + .17

Original Data I have to break apart and sum is listed below.
000000025000001000000283711000025000037000054000000017

My total should look like this:
037309807

Any Ideas as to how I would go about this?

August 28, 2015 at 12:15 PM

Jason Yoder, MCT said…

Matt,

Check out this posting.
http://www.mctexpert.blogspot.com/2015/08/string-manipulationcustom-problem.html

August 28, 2015 at 1:59 PM

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog