split_column_into_table
Move what a column repeats into a table of its own: ONE record of a new table per different value of the column (a supplier, a client, a category named on many rows), made from the values the table already holds — never invented — and a link field added to the table, filled for every row. Use it for «split X into their own table», «make suppliers a separate table», «normalise». The old columns stay as they are; the answer says what to tell the person about them. Do NOT use create_form for this: it makes an empty table. It is also the FIRST step of a list that depends on another field when that field is a plain dropdown (Stage → Check point): split the dropdown — its options become the parents' table — then link the children's column to it with into_table.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"app_id": "<app_id>",
"entity_id": "<entity_id>",
"column": "<column>"
},
"name": "split_column_into_table"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| app_id | Yes | Project ID (from list_projects) | |
| column | Yes | The field (name or id) whose values name the things — «Supplier» | |
| entity_id | Yes | The table that holds the column now | |
| into_table | No | A table the project ALREADY has (name or id) whose rows the column names: no table is made, the column is linked to that table's rows with the same values — e.g. the stage dropdown of «Check points» linked to «Stages», so a list on another form can depend on it | |
| table_name | No | The new table's name, in the person's language — «Suppliers» | |
| with_columns | No | Other fields of the same table that describe the same thing and go with it — «Supplier email», «Supplier phone» |