Hi Charles,

Worth the read is  RE: Using ISHRemote can I filter results where Version is less than or equal to a value? 

 Some code snippets giving the ASAP to unblock as inspiration. I tested them on 15.2.0 but I think they work on 14SP4/14.0.4 as well.

# As version is a string field, you can do an exact match
$requestedMetadata = Set-IshMetadataFilterField -Level Version -Name VERSION -FilterOperator Equal -Value '15'
Get-IshPublicationOutput -LogicalId GUID-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -MetadataFilter $requestedMetadata
# As you are then updating the version level, it would be a good optimization to do that only once for that version and not for every PublicationOutput below (e.g. English PDF, French PDF, English...)

# Regarding version compare...
# FISHBRANCHNR is a system field which you need to explicitly get
# you get ALL of them all the time, if you specify $ishSession.DefaultRequestedMetadata='All'
$requestedMetadata = (Set-IshRequestedMetadataField -Level Version -Name FISHBRANCHNR)
$p = Get-IshPublicationOutput -LogicalId GUID-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -RequestedMetadata $requestedMetadata

# to give you an idea of what we retrieved, print the below
# where the version is just an integer, no branched version, then fishbranchnr is zero... in turn you can use PowerShell -lt operator when cast to an [int]
$p | Select-Object ishref,version_version_value,fishbranchnr_version_value

# Below is a client-side, so in PowerShell calculation, when there are no branches
$p | ForEach-Object { 
        if (($_.fishbranchnr_version_value -eq '0') -and ([int]($_.version_version_value) -gt 10)) { Write-Output $_ }
    }

# when there are branches you could consider going 'manual selection' by
$p | Out-GridView -PassThru

Best wishes,
Dave

One other quick query. The objects I'm editing have the ISHMetadataBinding data type. I am able to set these values correctly - ie when I replace the Value with a backend ID like /1/2/3/4, it's correctly stored, and I see the correct full text string when I open the publication properties, populated by the metadatabinding. 

However, when I run this:
Get-IshMetadataField -IshSession $ishSession -Name "FINFAPRODUCTMETADATA" -Level Version -ValueType Value

The full text strings are retrieved instead of the IDs, which are what I need. What am I missing here? Changing the ValueType to element or ID doesn't help either. 

Btw, the reason I need this because I've realized I need to get the existing value first, as multiple values are already in this metadata field in many cases. 

Thanks for any help!

Hi Charlie,

Over the years ISHRemote defaults the -RequestedMetadata to human readable fields. The Id you are looking for is part of the System fields. The most optimal way to add this to the request is in the example below. Where I also gave you some inspiration for the PowerShell read-only PSNoteProperty shortcuts versus lengthy but still supported/correct Get-IshMetadataField usage.

PS C:\PRIVATE\OneDrive\CODE\ISHRemoteScript> $p=Get-IshPublicationOutput -LogicalId GUID-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -RequestedMetadata (Set-IshRequestedMetadataField -Level Logical -Name FISHMBPRODUCT -ValueType Id)

PS C:\PRIVATE\OneDrive\CODE\ISHRemoteScript> $p[0] | Get-IshMetadataField -Level Logical -Name FISHMBPRODUCT -ValueType Id
VPRODUCTFAMILYTRIDIONSITES
PS C:\PRIVATE\OneDrive\CODE\ISHRemoteScript> $p[0] | Get-IshMetadataField -Level Logical -Name FISHMBPRODUCT -ValueType Value
Tridion Sites (200)

PS C:\PRIVATE\OneDrive\CODE\ISHRemoteScript> $p[0].fishmbproduct_logical_id   
VPRODUCTFAMILYTRIDIONSITES
PS C:\PRIVATE\OneDrive\CODE\ISHRemoteScript> $p[0].fishmbproduct_logical_value
Tridion Sites (200)

People that want more insights in what fields to use, check Get-IshTypeFieldDefinition or have a look on [Sample \- Descriptive, Basic and All Fields](github.com/.../ReleaseNotes-ISHRemote-0.7.md

Best wishes,
Dave

That's great Dave, thanks for the thorough explanation!

best,

Charlie

That's great Dave, thanks for the thorough explanation!

best,

Charlie