Hola Robert,
Have you found a workaround for this?
When using a working table to support a custom form we normally have just one row. I’d like to be able to use some array/lookup or other columns to make this happen. I’m also not able to feed the choice column from relation columns in that single row working table.
Any ideas?
Thanks
Probably a bit late for Bob, so I’ll jump in here.
The restriction still applies. The source of a choice component can only be a single column with multiple rows, or a multiple relation.
If you have an array of values, then what you would need to do is create additional rows in your working table - enough to cater for the maximum number of choices - and then expand the array into multiple rows using the Row Index → Single Value method. Or alternatively, you could do the same in a separate table.
If the relation column in your working table is a multiple relation, then you should be able to use that.
1 Like
An unethical approach but works!
You can convert each entry in the comma seperated column to go into set no of rows in a temp column in another table!
But, then max no applies!
As the rows that you create in the temp table would be finite, your options also needs to be finite!
If you have 10 options, create 10 rows.
Get the array in a single value column!
Create a column with numbering 1,2,3,4,5,6,7,8,9,10!
Write JS or use array column to get that element from the array!
And voila you would have options in rows which can be used for dropdown!
It may take time to get the data!
Also, it might be difficult in a form to put it if you havent fetched single value in the screen before the form!
Cannot happen real time in a form!