Can you provide us with an original example (i.e. before the script is called) of the file you're reading from on line 2?
There are a few things that don't make sense in the first output example when compared to how the script is written. Having the original example/JSON template will help.
In short though, you'd ideally want to work with the List type.
One thing you don't want to be doing is constantly reading from and writing to the file every iteration of the loop, as the current script does. That will scale very, very poorly as the object count goes up, so unless you're working with a very small data set, I'd be avoiding this approach.
Here's a somewhat abstract example - given the above caveats - using the List approach.
Bogus JSON template used
{
"Environment": {},
"Profiles": {
"Services": [
{
"Name": "A"
},
{
"Name": "B"
},
{
"Name": "C"
},
{
"Name": "D"
},
{
"Name": "E"
},
{
"Name": "F"
}
]
}
}
Conceptual code only
$JsonObjects = Get-Content .\forum.json | ConvertFrom-Json;
$ServicesObjects = [System.Collections.Generic.List[PSCustomObject]]$Data.Profiles.Services;
$ServicesObjects.FindIndex({ param($Entry); $Entry.Name.Equals("E") });
$ServicesObjects.Insert($ServicesObjects.FindIndex({ param($Entry); $Entry.Name.Equals("E") }), ([PSCustomObject] @{ Name = "WhateverYouLike"; }));
This conceptual code is purely to demonstrate how to work with the List type. It is not a complete solution to your question.
Here's the output from this conceptual example.
Once you've finished inserting items wherever you want them, you can then re-assign the List object back onto the broader JSON data set from where you obtained it and push that back out to JSON using the usual ConvertTo-Json commandlet, after which you can dump it back to file or do whatever you want to do.
$Data.Profiles.Services = $ServicesObjects;
$Data | ConvertTo-Json;
Cheers,
Lain
Hey, Vivek.
That's an example of something called a "predicate".
The simplest explanation I can provide is that where you see a "predicate" as a parameter, instead of asking for a data type like "string", "int", "bool" etc., it's asking for a block of code, which is what you see between the curly braces (i.e. those braces indicate a "scriptblock".)
Here's some examples of predicates:
From PowerShell itself
The corresponding Microsoft's .NET class documentation
- List<T>.Exists(Predicate<T>) Method (System.Collections.Generic) | Microsoft Docs
- List<T>.FindIndex Method (System.Collections.Generic) | Microsoft Docs
So, that's the high-level answer. But what am I specifically doing with that line?
I'm looking for the position in the List "array" of the letter "E".
Breakdown:
param($Entry)
With a predicate, your code block is executed against each item within the List "array".
For each iteration, the current list item being checked is passed into your predicate as a parameter, and you receive - or "fetch" - this list item parameter using the "param()" definition.
So, this part is simple me fetching the list item as a parameter and assigning it to a variable I named $Entry. This allows me to do stuff later with the $Entry variable.
$Entry.Name.Equals("E")
There's probably nothing I need to explain here since it's a basic statement. The key thing is this is where I'm making use of the list item found in the $Entry parameter.
Since I'm working with your JSON as objects, "Name" is simply derived through being a property defined in your JSON template.
Some other basic examples of predicates
Cheers,
Lain
Accepted Solutions
Can you provide us with an original example (i.e. before the script is called) of the file you're reading from on line 2?
There are a few things that don't make sense in the first output example when compared to how the script is written. Having the original example/JSON template will help.
In short though, you'd ideally want to work with the List type.
One thing you don't want to be doing is constantly reading from and writing to the file every iteration of the loop, as the current script does. That will scale very, very poorly as the object count goes up, so unless you're working with a very small data set, I'd be avoiding this approach.
Here's a somewhat abstract example - given the above caveats - using the List approach.
Bogus JSON template used
{
"Environment": {},
"Profiles": {
"Services": [
{
"Name": "A"
},
{
"Name": "B"
},
{
"Name": "C"
},
{
"Name": "D"
},
{
"Name": "E"
},
{
"Name": "F"
}
]
}
}
Conceptual code only
$JsonObjects = Get-Content .\forum.json | ConvertFrom-Json;
$ServicesObjects = [System.Collections.Generic.List[PSCustomObject]]$Data.Profiles.Services;
$ServicesObjects.FindIndex({ param($Entry); $Entry.Name.Equals("E") });
$ServicesObjects.Insert($ServicesObjects.FindIndex({ param($Entry); $Entry.Name.Equals("E") }), ([PSCustomObject] @{ Name = "WhateverYouLike"; }));
This conceptual code is purely to demonstrate how to work with the List type. It is not a complete solution to your question.
Here's the output from this conceptual example.
Once you've finished inserting items wherever you want them, you can then re-assign the List object back onto the broader JSON data set from where you obtained it and push that back out to JSON using the usual ConvertTo-Json commandlet, after which you can dump it back to file or do whatever you want to do.
$Data.Profiles.Services = $ServicesObjects;
$Data | ConvertTo-Json;
Cheers,
Lain