[Bug]-[80]:Multi Tree Select not correctly populating its selectedOptionValues field.

[ghost]

Is there an existing issue for this?

• I have searched the existing issues

Description

When accessing selected item values of a Multi Tree Select (MTS) widget and empty array is returned. The values exist under MTS.selectedOptionValueArr but not MTS.selectedOptionValues. There is an example here.

Steps To Reproduce

1. Make a new Multi Tree Select widget
2. Add this as the data:

[
  {
    "label": "Sovereign Team",
    "value": 1,
    "children": [
      {
        "label": "Laguna",
        "value": 4
      },
      {
        "label": "spark-c",
        "value": 9
      }
    ]
  },
  {
    "label": "OneShot Team",
    "value": 3,
    "children": [
      {
        "label": "Amelia",
        "value": 8
      }
    ]
  }
]

3. Select any amount of values.
4. Attempt to display or access these through MTS.selectedOptionValues

Public Sample App

https://app.appsmith.com/applications/623c8b404d9aea1b062b3047/pages/623c8b404d9aea1b062b304a

Version

Cloud

[dilippitchika]

@AS-Laguna did a user raise this?

[ghost]

@dilippitchika No, I found it.

[techbhavin]

@somangshu @dilippitchika @sbalaji1192

Here I analyze tree-select children have an array of objects of label and value. both have a value type of must be a string if we put has a number (as shown in an issue) then it will be not working expected.

expected data :

[ { "label": "Sovereign Team", "value": "1", "children": [ { "label": "Laguna", "value": "4" }, { "label": "spark-c", "value": "9" } ] }, { "label": "OneShot Team", "value": "3", "children": [ { "label": "Amelia", "value": "8" } ] } ]

[dilippitchika]

Thanks for pointing this @techbhavin, @Tooluloope @somangshu is this something we can pick up in select widget stability changes? We updated the select and multi-select to support this and we can add same functionality here as part of that epic.

[Tooluloope]

This should be an easy fix since multiTreeSelect doesn't have serverside filtering
@techbhavin The problem here is that we stringify before we search.

We could make a derived property file. Then write a comprehensive function to recursively search the nested Options for the value?

[dilippitchika]

@Tooluloope i believe we should add server side filtering for tree and multi tree select as well to make it consistent with the select family.

This was an issue I had created to track it - #10847

All the items in select, multi, tree and multi tree should share some common things which should be tackled as part of stability epic.

[Tooluloope]

Nice,
Got it @dilippitchika

[dilippitchika]

Ok so let's add this issue to - #11902

@techbhavin thanks for pointing this, we will pick this up as part of a separate epic. You don't have to pick it up now.

[dilippitchika]

Stats

Stat	Values
Reach	20
Effort (months)	0.5