You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally ISHRemote was a thin layer on top of the API, so implementation of Set-IshLovValue was over IshSession.ListOfValues25.UpdateValue(LovId, LovValueId, Label, Description, Active); in turn forcing all properties as mandatory on the cmdlet.
Since the introduction of Active/Inactive in the user interfaces since 14SP1/14.0.1 the toggling of Active to Inactive is more important.
Best implementation is
Make parameters optional, also extra Pester tests
When not all parameters are specified, add a Get operation to default the missing properties in the UpdateValue API call
Other considered options are
Extend Set-IshMetadataField to overwrite “fields” of LovValue objects…
Get-IshLovValue … | Set-IshMetadataField -Active $False | Set-IshLovValue
Or await a better API call :-)
The text was updated successfully, but these errors were encountered:
Originally ISHRemote was a thin layer on top of the API, so implementation of
Set-IshLovValue
was overIshSession.ListOfValues25.UpdateValue(LovId, LovValueId, Label, Description, Active);
in turn forcing all properties as mandatory on the cmdlet.Since the introduction of Active/Inactive in the user interfaces since 14SP1/14.0.1 the toggling of Active to Inactive is more important.
Best implementation is
Get
operation to default the missing properties in theUpdateValue
API callOther considered options are
Get-IshLovValue … | Set-IshMetadataField -Active $False | Set-IshLovValue
The text was updated successfully, but these errors were encountered: