Yes, it is possible indeed via the valueOptions
. In this option, you specify a separate data source table datasource_mapping_table
containing three columns: plan_key, plan_value_1 (for the valueColumn
), plan_value_2 (for the labelColumn
).
plan_key | plan_value_1 | plan_value_2
a | b | b
a | c | c
Then, in the app you configure this code to specify how the Join on the plan_key should occur. In each key’s dropdown, all the plan_value_1 corresponding to plan_key are going to be visible and selectable:
{
"id": "ele_table_dropdown_column",
"config": {
"columns": [
{
"name": "plan_key",
"label": "Plan Key",
"width": "160px",
"edit": true
}
],
"dataLabels": true,
"download": {
"fileName": "Download File Name",
"full": true,
"type": "excel"
},
"rangeFilter": true,
"valueFilter": true,
"editing": {
"labels": {
"startEditing": "Edit Table",
"stopEditing": "Cancel"
},
"edit": true,
"add": false,
"delete": false,
"saveToMicroservice": {
"id": "workflowID",
"targetProjectId": "projectId",
"fullDeletedRows": false,
"synchronizeResults": true,
"variableAssignments": [
//optional variable to pass to the WF when editing
{
"variableName": "var_1", // (Technical) Name of the variable
"variableValue": "my_value_var_1"
}
]
},
"lockAppWhileEditing": true,
"lockDataUpdatesWhileEditing": false,
"valueOptions": [
{
"column": "plan_key",
"source": "datasource_mapping_table",
"valueColumn": "plan_value_1",
"labelColumn": "plan_value_2",
"allowNewValues": false,
"syncSets": []
}
]
}
},
"source": "data_table_datasource",
"sourceOptions": {
"sql": "SELECT i.* FROM inputTable i "
},
"styles": {},
"type": "table"
}