- \nWhen working with output files it is sometimes necessary to create some sort of uniqueness factor. The purpose of this uniqueness factor is to make sure that the files is not overwritten by a subsequent re-running of a script manually or even as part of a scheduled task. Other factors that may necessitate this uniqueness are keeping track of when a log file or results file were written for testing or eventually for production.
\n** One caveat to making the file name unique is that it could make it harder to find if a script needs the output for a later operation. We covered how to keep track of these in a previous Tip of the Week.<\/em>
\nUniqueness Factor Type – Date<\/u>
\nOne of the easiest uniqueness factors to use when generating a file name is a current date or current date and time. Depending on how often a script process is run and the log file generated, should help determine what date format to use. This is import as the Get-Date cmdlet in PowerShell can be used to formulate the date and time to something simple to very complete. Also remember that if using this for files names do not use characters that cannot be placed in file names like backslashes.
\nThe default output of Get-Date is completely useless for file names:
\n
![\"\"](\"https:\/\/i0.wp.com\/practicalpowershell.com\/wp-content\/uploads\/2020\/03\/PSTIP20181001-01.jpg?ssl=1\")
<\/a>\nAs such we’ll need to tweak this output to the format we need. Some formatting conventions to help us move forward:
\nDate:
\nD Date in mm\/dd\/yy format (06\/14\/06)
\nx Date in standard format for locale (09\/12\/07 for English-US)
\nYear:
\nC Century (20 for 2006)
\nY Year in 4-digit format (2006)
\ny Year in 2-digit format (06)
\nG Same as ‘Y’
\ng Same as ‘y’
\nMonth:
\nb Month name – abbreviated (Jan)
\nB Month name – full (January)
\nh Same as ‘b’
\nm Month number (06)
\nWeek:
\nW Week of the year (00-52)
\nV Week of the year (01-53)
\nU Same as ‘W’
\nDay:
\na Day of the week – abbreviated name (Mon)
\nA Day of the week – full name (Monday)
\nu Day of the week – number (Monday = 1)
\nd Day of the month – 2 digits (05)
\ne Day of the month – digit preceded by a space ( 5)
\nj Day of the year – (1-366)
\nw Same as ‘u’
\nTime:
\np AM or PM
\nr Time in 12-hour format (09:15:36 AM)
\nR Time in 24-hour format – no seconds (17:45)
\nT Time in 24 hour format (17:45:52)
\nX Same as ‘T’
\nZ Time zone offset from Universal Time Coordinate (UTC) (-07)
\nHour:
\nH Hour in 24-hour format (17)
\nI Hour in 12 hour format (05)
\nk Same as ‘H’
\nl Same as ‘I’ (Upper-case I = Lower-case L)
\nMinutes & Seconds:
\nM Minutes (35)
\nS Seconds (05)
\ns Seconds elapsed since January 1, 1970 00:00:00 (1150451174.95705)
\nSpecial Characters:
\nn newline character (\\n)
\nt Tab character (\\t) <\/em>
\nAs you can see there are a lot of options for formatting the output of the Get-Date cmdlet. First, we’ll start simple and build out to a complex date format that can be used for file names.
\nDay, Month, Year<\/em>
\nNow depending on your locality, the exact arrangement of the digits will differ. The key is to remember what you used for your date format. Because June 6, 2018 (20180606, 2018-06-06, 06-06-2018, 06-06-2018) is an easy one to work with. Whereas December first may cause confusion (20181201, 2018-12-01, 12-01-2018, 01-12-2018).
\nyyyy-mm-dd 2018-09-25
\nyyyy-dd-mm 2018-25-09
\nmm-dd-yyyy 09-25-2018
\nDd-mm-yyyy 25-09-2018<\/em>
\nFor a script that is run on a daily basis, this is a good, simple data to return. Applying this to a log or data file is simple, like so:
\n[sourcecode language=”powershell”]
\n$OutPutFileNameBase1 = 'AllMailboxes-Cloud'
\n$LogFileNameBase1 = 'ScriptErrorLog'
\n$CurrentDate = Get-Date -Format yyyy-mm-dd
\n$OutPutFileNameFull1 = $OutPutFileNameBase1+"-"+$CurrentDate
\n$LogFileNameFull1 = $LogFileNameBase1+"-"+$CurrentDate
\n[\/sourcecode]
\n
<\/a>\nNow we have a simple and unique name (if the script is run daily) allowing us to use this for logs, output and error files, for example. Now what if the script runs more often or needs a finer pinpoint on when the output file was generated? Well, we need to add some more detail to the date added to the file name.
\n[sourcecode language=”powershell”]
\n$CurrentDate = Get-Date -Format yyyymmdd-hhmmss
\n[\/sourcecode]
\nUsing the previous code as an example and changing the date format to be more specific, the code looks like this:
\n[sourcecode language=”powershell”]
\n$OutPutFileNameBase1 = 'AllMailboxes-Cloud'
\n$LogFileNameBase1 = 'ScriptErrorLog'
\n$CurrentDate = Get-Date -Format yyyyymmdd-hhmmss
\n$OutPutFileNameFull1 = $OutPutFileNameBase1+"-"+$CurrentDate
\n$LogFileNameFull1 = $LogFileNameBase1+"-"+$CurrentDate
\n[\/sourcecode]
\nThe output then looks like this:
\n
<\/a>\nUniqueness Factor Type – Random Number<\/em>
\nAnother way to generate unique files is to keep the same base file name and add a random number to the end of the file. Depending on how often these files are generated, the number of digits for the random number may need to be high. Because there is absolutely no guarantee that the filename will be unique, you may need to build in logic to check for an existing file of that same name to prevent overwriting files. This caveat is one of the biggest reasons to use the Date in the file name and not a random number.
\nIf we look for cmdlets in PowerShell that contain the word ‘Random’ in it:
\nGet-Command *random*
\nWe see that there is only one cmdlet that meets that criteria. If we type the cmdlet into a PowerShell session, it generates a random 9+ digit number. Below are three samples from the cmdlet when run one after the other:
\n1131270443
\n556361410
\n1225835655<\/em>
\nIn order to tweak the output, you can set a minimum number, a maximum number and even provide a seed number to help generate the random numbers. For creating file names, the default length will probably be sufficient:
\n[sourcecode language=”powershell”]
\n$Random = Get-Random
\n[\/sourcecode]
\nSo using the code example from the previous example, we get something like this:
\n[sourcecode language=”powershell”]
\n$OutPutFileNameBase1 = 'AllMailboxes-Cloud'
\n$LogFileNameBase1 = 'ScriptErrorLog'
\n$Random = Get-Random
\n$OutPutFileNameFull1 = $OutPutFileNameBase1+"-"+$Random
\n$LogFileNameFull1 = $LogFileNameBase1+"-"+$Random
\n[\/sourcecode]
\nIf we are worried about duplicate file names, we can introduce logic to handle this:
\n[sourcecode language=”powershell”]
\n$RandomCheck1 = $OutPutFileNameBase1+"-"+$Random
\nIf (-NOT (Test-Path $RandomCheck1)) {$OutPutFileNameFull1 = $OutPutFileNameBase1+"-"+$Random}
\n$RandomCheck2 = $LogFileNameBase1+"-"+$Random
\nIf (-NOT (Test-Path $RandomCheck2)) {$LogFileNameFull1 = $LogFileNameBase1+"-"+$Random}
\n[\/sourcecode]
\nNow when we run this, we’ll get these names for the files:
\n
<\/a>\nThat’s it. Now you can go create your random files for output from your scripts.<\/p>\n","protected":false},"excerpt":{"rendered":"
Unique output files: Date Random number Append Noclobber When working with output files it is sometimes necessary to create some sort of uniqueness factor. The purpose of this uniqueness factor is to make sure that the files is not overwritten by a subsequent re-running of a script manually or even as part of a scheduled […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":[],"rop_publish_now_history":[],"rop_publish_now_status":"pending","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-538","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"yoast_head":"\n