How can I map the value of one “Select” field to map another text field?

hi community,

My questions:-
How can I map a client‑to‑multiple‑RM relationship across several “Select” fields in a Camunda 8 Cloud Form?

How Can I map a clint to single RM relationship across several?

can you guide how to resolve that issue below i paste my json this single value
{
“components”: [
{
“label”: “Select”,
“values”: [
{
“label”: “Fortune Brands”,
“value”: “ROD O’HARA”
},
{
“label”: “ACF Industries”,
“value”: “MARTYNA MOTYKA”
}
],
“type”: “select”,
“layout”: {
“row”: “Row_1qhzg8d”,
“columns”: null
},
“id”: “Field_0e5etkm”,
“key”: “select_jkxp4”
},
{
“label”: “Select”,
“values”: [
{
“label”: “RmName”,
“value”: “value”
}
],
“type”: “select”,
“layout”: {
“row”: “Row_1dz7sdy”,
“columns”: null
},
“id”: “Field_1jiigu1”,
“key”: “select_zvj79i”
}
],
“type”: “default”,
“id”: “Form_1pmlscw”,
“executionPlatform”: “Camunda Cloud”,
“executionPlatformVersion”: “8.7.0”,
“exporter”: {
“name”: “Camunda Modeler”,
“version”: “5.37.0”
},
“schemaVersion”: 18
}

If I understand your question correctly, you are trying to build dependent fields — meaning each time there is a change on the first field, the option values of the second select field change, right?

If that’s correct, this can be configured in a Camunda form using FEEL expressions.

The key points are:

  1. You should configure the option sourceof the second select (the dependent one) as a Expression (FEEL), not as static values like you have in your JSON.

  2. The options expression can use if-else logic (or match) to populate the options based on what the user selects in the first select field.

Here’s a simple example using two select fields: Country → City:

{
   "executionPlatform":"Camunda Cloud",
   "executionPlatformVersion":"8.7.0",
   "schemaVersion":18,
   "id":"Form_fieldsDependency",
   "components":[
      {
         "label":"Country",
         "values":[
            {
               "label":"France",
               "value":"France"
            },
            {
               "label":"Germany",
               "value":"Germany"
            },
            {
               "label":"USA",
               "value":"USA"
            }
         ],
         "type":"select",
         "layout":{
            "row":"Row_0swcbfv",
            "columns":null
         },
         "id":"Field_1dr8138",
         "key":"country"
      },
      {
         "label":"City",
         "type":"select",
         "layout":{
            "row":"Row_0zru3ev",
            "columns":null
         },
         "id":"Field_1htncwl",
         "key":"city",
         "valuesExpression":"=if country = \"France\" then [{\"label\": \"Paris\",\"value\": \"Paris\"},{\"label\": \"Toulouse\",\"value\": \"Toulouse\"}] else if country = \"Germany\" then [{\"label\": \"Munich\",\"value\": \"Munich\"},{\"label\": \"Cologne\",\"value\": \"Cologne\"}] else if country = \"USA\" then [{\"label\": \"California\",\"value\": \"California\"},{\"label\": \"Texas\",\"value\": \"Texas\"}] else []"
      }
   ],
   "type":"default"
}
  • When the user selects France, the second dropdown will show Paris and Toulouse.

  • When the user selects Germany, it will show Munich and Cologne.

This approach is exactly what you need for client → RM mappings as well: the first select is your client, and the second one (RM) is filled dynamically using a FEEL expression.

Let me know if this fixes your problem!

Hello!

To map client-to-RM relationships in Camunda 8 Cloud Forms, use one “Select” field for one-to-one mapping, where each client links to a single RM. For one-to-many, use multiple fields or external logic to dynamically populate RM options based on the selected client, since native dynamic linking isn’t supported in Camunda Forms.