syncedOptions not working in combination with valueMapping

We are using syncedOptions in an editable tables, to have synced dropdowns
This is working as expected.
Now we added valueMapping for one of the columns and if the user now enters the edit mode of the editable table the values of the depended dropdown column get lost.
Is syncedOptions still the way to go or is it possible to sync dropdown values in another way since the syncset rework?
Thank you in advance

Code valueOptions:
“valueOptions”: [
{
“column”: “providing_cost_center_id”,
“source”: “project_fte_forecast_add_qualification_datasource”,
“valueColumn”: “cost_center_id”,
“labelColumn”: “cost_center_name”,
“allowNewValues”: false,
“syncSets”: []
},
{
“column”: “qualification_name”,
“source”: “project_fte_forecast_add_qualification_datasource”,
“valueColumn”: “qualification_name”,
“allowNewValues”: false,
“syncSets”: [],
“syncedOptions”: [
{
“sourceColumn”: “providing_cost_center_id”,
“targetColumn”: “cost_center_id”
}
]
}
]

Code valueMapping:
“valueMapping”: [
{
“column”: “providing_cost_center_id”,
“source”: “project_fte_forecast_add_qualification_reduced_datasource”,
“joinColumn”: “cost_center_id”,
“targetColumn”: “cost_center_name”
}
]

This appears to be a bug in Apps. When setting filters on the synced columns, only the visible value (which may be mapped) is taken into account. Instead, the unmapped value should be used for syncedOptions.

This was noted as a bug and is tracked under the internal ticket ID ABVI-1114.

1 Like

The fix tracked under ABVI-1114 has been merged into our mainline development branch and will be part of the next release of ONE DATA Apps.

The fix for the faulty behavior is part of Apps Client 1.80.1, released on 12.01.2021.

1 Like