Administration of Active Directory does not have to be hard. Too often what should be a simple task is made more difficult than it needs to be.The solution? Hyena from SystemTools Software. With ease-of-use as well as powerful importing and bulk updating capabilities.
powershell : what's wrong ?
function ManageAdUsers($CsvFile)
{
$MyVariable = 99
$SAM = ""
$bAlreadyProcessed = $false
$Items = Import-Csv -path "$CsvFile" –delimiter ";" | foreach ($Item in $Items) {Write-Host $Item}
--> give this error
PS M:\ICT Manager\Scripts\PS1> .\importad.ps1
Unexpected token 'in' in expression or statement.
At M:\ICT Manager\Scripts\PS1\Import
+ $Items = Import-Csv -path "$CsvFile" -delimiter ";" | foreach ($Item in <<<<
$Items) {Write-Host $Item}
+ CategoryInfo : ParserError: (in:String) [], ParseException
+ FullyQualifiedErrorId : UnexpectedToken
{
$MyVariable = 99
$SAM = ""
$bAlreadyProcessed = $false
$Items = Import-Csv -path "$CsvFile" –delimiter ";" | foreach ($Item in $Items) {Write-Host $Item}
--> give this error
PS M:\ICT Manager\Scripts\PS1> .\importad.ps1
Unexpected token 'in' in expression or statement.
At M:\ICT Manager\Scripts\PS1\Import
+ $Items = Import-Csv -path "$CsvFile" -delimiter ";" | foreach ($Item in <<<<
$Items) {Write-Host $Item}
+ CategoryInfo : ParserError: (in:String) [], ParseException
+ FullyQualifiedErrorId : UnexpectedToken
Asked:
4
2
2 Solutions
Because you're already in the pipeline, when you pass through a list you don't need to specify a holding variable to work through it as this is already implied and handled by the $_ parameter.
So you can just use
$_ refers to the current object from the pipeline.
So you can just use
$Items = Import-Csv -path "$CsvFile" –delimiter ";" | foreach {Write-Host $_}
$_ refers to the current object from the pipeline.
Daryl, this is not correct. Your code is assigning the final result of the pipe, which is nothing because nothing has been put into the pipeline again. However, just removing $Items = is sufficient.
Qlemo, it is correct in terms of the pipeline always takes precedence. Hence it will still write-out to the screen all the contents of the imported CSV file.
However, you do bring up a valuable point. Nothing will actually be assigned to the $items variable (when I tested it I was only checking info wrote to the screen, and forgot about the variable assignment). Also you will need to specify your field header otherwise it will take the first item as the header (assuming there isn't already a header). So
I am assuming he wants to assign the contents to a variable as well as writing out to the screen?
However, you do bring up a valuable point. Nothing will actually be assigned to the $items variable (when I tested it I was only checking info wrote to the screen, and forgot about the variable assignment). Also you will need to specify your field header otherwise it will take the first item as the header (assuming there isn't already a header). So
$items = Import-Csv -path "$CsvFile" –delimiter ";" -header "name"
$items | foreach {write-host $_.name}
I am assuming he wants to assign the contents to a variable as well as writing out to the screen?
If that last assumption is correct, footech's code is the way to go. We cannot tell, because the original code posted is only sample code without much real value ...
Got bored .. parenthesise are your friend ..
($items = Import-Csv -path "$CsvFile" –delimiter ";" -header "name") | foreach {write-host $_.name}
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
Open in new window