- Latest Posts & Videos, All Posts, and All Videos are served from the CONTENT DATABASE, based on a few properties:
- Type: Post or Video plus Feature As a Feature post or video, it also serves to the home page as a Latest Post or Latest Video. Consider only having 1-3 Feature at a time to avoid cluttering the page.
- Status: Live - a post or video marked as Draft will not serve to this page or the home page.
- Type: Post or Video
- Status: Live
- Make sure to replace the text in the properties: Title, Excerpt, and Published Date so Post display correctly like this:
I was recently working on the TOPdeskPS module and came across the need to access a subproperty of an object that was being input.
[pscustomobject]@{
Property1 = 'value'
Property2 = ([pscustomobject]@{
Subproperty1 = 'value2'}
)}Using the sample above, we need to access BOTH Property1 and Property2. We could accept a pscustomboject as input, but I’d prefer allowing to use to specify their own value for Subproperty1 or Property1 if they want to override the value that would be in the incoming object.
This is a representation of the actual object that I was working with.
[pscustomobject]@{
AssetId = 'ABCD-1234'
locations = ([pscustomobject]@{
linkId = 'DEFG-5678'
branch = 'branchName'
})
}In our above sample I need both the AssetId and the linkId from the incoming object. I ended up using ValuefromPipelinebyPropertyName and utilizing a parameter alias so I could capture the ‘Locations’ property from the incoming object. Inside my function I then refer to the LinkId by using $Linkid.LinkId
Now let’s create a function that allows us to view this in action. Run this function in your console so we can access it
function Get-InputSubproperty{
param (
[Parameter(ValuefromPipelinebyPropertyName)]
$AssetId,
[Parameter(Valuefrompipelinebypropertyname)]
# we set an alias so that we can capture the parent property of our LinkId, locations.
[Alias('locations')]
$LinkId
)
process {
[pscustomobject]@{
AssetId = $AssetId
# We need to access the property inside $LinkId.
# We captured the parent property, Locations, from the input object so we need to refer to the linkId inside the object.
LinkId = $LinkId.linkid
}
}
}Now let’s try accessing the subproperty.
[pscustomobject]@{
AssetId = 'ABCD-1234'
locations = ([pscustomobject]@{
linkId = 'DEFG-5678'
branch = 'branchName'
})
} | Get-InputSubpropertyAs you can see, we are able to easily access the linkId with nice pipeline support.
This is the body of the code that I ended up with.
Closing Thoughts
If you work with API’s and haven’t tried using PowerShell to do so then I highly recommend you give it a shot. I’m always so pleased with how easy it is to make great tools with PowerShell that provide great value.
I thought this was a pretty clever workaround. Thanks to Chris Gardner for the idea. I highly recommend that you join the PowerShell slack community if you haven’t already. You can use Discord, Slack, or IRC.