Object property names/values differ from API

[dsoper2]

Customer feedback looking for ways to use the same object property names and values as the direct API. For example, bios policy SelectMemoryRasConfiguration values are platform-default/adddc-sparing/etc. in the API, but follow PowerShell naming conventions in the SDK (PlatformDefault/AdddcSparing/etc.). Filters and other API operations would need to use API naming so conversions are needed from what SDK objects return. There's also not a way I know of to get the meta data for cmdlets like there is in UCS PowerTool (Get-UcsCmdletMeta), so the user may not be sure of valid property values if they don't match the schema. I can submit another issue with a request for cmdlet meta data if needed.

[vvb]

@dsoper2 that is PowerShell's convention. When using PowerShell, the enum constants auto-complete on hitting tabs. So, you really don't need to remember the exact convention on the value.

We don't have a cmdlet to get meta yet. We will work on adding one.