How to rewrite ENUM selected values with seperate expression.

[JamesHutchinsonHV]

I have an enum that obtains its list or from at API using fnRestBasic.

My selections in the main form are stored as portPairs

  - name: portPairs
    label: Port Pairs
    type: enum
    required: true
    expression: fn.fnRestBasic('get','http://172.16.169.116//storage_array/$(array.serial_number)/portpairs?hostType=any&hostType=$(hostType.name)','','')
    horizontal: false
    multiple: true
    outputObject: true
    sticky: true

This results in the following in extravars, if multiple portPairs are selected:

"portPairs":[
{
"hostType":"ANY",
"primaryPort":"CL1-C",
"secondaryPort":"CL2-C"
},
{
"hostType":"Windows",
"primaryPort":"CL1-A",
"secondaryPort":"CL2-A"
}
],

I want to flatten this in to a list of ports, for example: ["CL1-C","CL2-C","CL1-A","CL2-A"] so I can use it in a table.
And to do this I was looking to use a separate expression in the main form and use "from" in the table enum.

However when I try initially to get the data in to a new variable (portList) via the expression I only get the following:

  - name: portList
    type: expression
    expression: $(portPairs)
    runLocal: false

Returns:

[
"ANY",
"Windows"
]

I know (portPairs) is an object as per the extravars because if I use this in my table enum the structure with hostType, primaryPort & secondaryPort is shown. but when I view the data in the main form via (portList) I only see a list of hostType's.

  - name: serverPaths
    label: Server WWN Mapping
    type: table
    required: true
    dependencies:
      - name: portPairs
        isValid: true
    tableFields:
      - name: serverWWPN
        label: Server WWPN
        type: text
      - name: storagePort
        label: Storage Port
        type: enum
        from: **portPairs**

What am I doing wrong?

[ansibleguy76]

So you want a single table with port 1 & port 2 and this multiple ?

[ansibleguy76]

you can do this with jq

expression: fn.fnJq($(portPairs),'[.[] | .primaryPort,.secondaryPort]')

[JamesHutchinsonHV]

With this I just end up with "null" for my (portList)

[ansibleguy76]

fields:
  - name: portPairs
    type: enum
    outputObject: true
    values:
      - hostType: ANY
        primaryPort: CL1-C
        secondaryPort: CL2-C
      - hostType: Windows
        primaryPort: CL1-A
        secondaryPort: CL2-A
    multiple: true
    placeholderColumn: "*"
    sticky: true
  - name: flat
    type: expression
    expression: fn.fnJq($(portPairs),'[.[] | .primaryPort,.secondaryPort]')

[ansibleguy76]

note the fn.fnJq() is a remote expression, not a local one. It uses the predefined function fnJq, which otherwise does not exist natively in Javascript.

[ansibleguy76]

or you can do it with local javascript

runLocal: true
expression: $(portPairs).flatMap(({ primaryPort, secondaryPort }) => [primaryPort, secondaryPort])

[JamesHutchinsonHV]

  - name: portList
    type: expression
    runLocal: true
    expression: $(portPairs).flatMap(({ primaryPort, secondaryPort }) => [primaryPort, secondaryPort])

Result:

[JamesHutchinsonHV]

I did intend to use this, but that's when I found that (portPairs) was not structured correctly.

The log also only shows:
2025-03-14 14:28:11:2811 info: Expression: ["ANY","Windows"]

[JamesHutchinsonHV]

My goal is to have a table where I can select from the portList dropdown and add a server MAC resulting in the following If I was to add mac to every port, one at a time via the table.

"serverPaths":[
{
"port":"CL1-C",
"mac":"xxxxxxx"
},
{
"port":"CL2-C",
"mac":"yyyyyyy"
},
{
"port":"CL1-A",
"mac":"zzzzzzzz"
},
{
"port":"CL2-A",
"mac":"fffffffffff"
}
]

[ansibleguy76]

fields:
  - name: portPairs
    type: enum
    outputObject: true
    values:
    - hostType: ANY
      primaryPort: CL1-C
      secondaryPort: CL2-C
    - hostType: Windows
      primaryPort: CL1-A
      secondaryPort: CL2-A
    multiple: true  
    placeholderColumn: "*"
  - name: flat
    type: expression
    runLocal: true
    expression: $(portPairs).flatMap(({ primaryPort, secondaryPort }) => [primaryPort, secondaryPort])

[ansibleguy76]

note the placeholderColumn: "*" => is required to expose all properties

[JamesHutchinsonHV]

Spot on that works, Thanks

[ansibleguy76]

[ansibleguy76]

fields:
  - name: portPairs
    type: enum
    outputObject: true
    values:
    - hostType: ANY
      primaryPort: CL1-C
      secondaryPort: CL2-C
    - hostType: Windows
      primaryPort: CL1-A
      secondaryPort: CL2-A
    multiple: true  
    placeholderColumn: "*"
  - name: flat
    type: expression
    runLocal: true
    expression: $(portPairs).flatMap(({ primaryPort, secondaryPort }) => [primaryPort, secondaryPort])
  - name: serverPaths
    label: Server WWN Mapping
    type: table
    required: true
    dependencies:
      - name: portPairs
        isValid: true
    tableFields:
      - name: serverWWPN
        label: Server WWPN
        type: text
      - name: storagePort
        label: Storage Port
        type: enum
        from: flat   

[JamesHutchinsonHV]

While on the subject how can I remove the previously selected ports from portList so they can't be selected more than once during the add process.

[ansibleguy76]

I'll make this a different discussion.