Column values based on another table's multi-select column values

[Admin_istrator]

Hi,

I have a table column with multi-select and input new items on. I am trying to extract the different cell values of that column into another table in individual rows. For eg in Table 1 multi select column I have options A and B selected. In Table 2, I would like to have Option A in one row and Option B in the next row. Thanks.

[Federico_Stefanato]

Hi @Admin_istrator,

please have a look at this basic sample and tell me if it works for you:

Maybe this is not the case, but as usual, with data re-structuring, it would be useful to understand the bigger picture as maybe this solution could be better addressed with a proper data model.

I hope this helps

[J_Pi]

Dear @Federico_Stefanato,

Thanks for the nice solution.
Will it be possible to add also a second column with the same button, either from the same table or another table?

[Federico_Stefanato]

Hi @J_Pi,
welcome to you too!

Sure, but it would be nice to have an idea: could you share or outline an example?

Thank you!

[Admin_istrator]

Hi @Federico_Stefanato,

Thanks for the solution! Is it possible to have the values work more like a lookup instead of an action? Using actions requires the automation to delete all rows in the table and then run the formula to prevent duplicates.

[J_Pi]

Dear @Federico_Stefanato,

I had some sharing issues that the Coda team managed to solve for me

It would be nice if you could guide me on this scenario:

Thanks for your time and patience

[Connor_McCormick]

There is not currently a way to do this without better access to Outer Current value. The only solution to this problem is Iterator Tables:

Tutorial: Iterator tables (CurrentValue workaround)

After answering the CurrentValue issue questions so. many. times, I finally recorded the tutorial on a Coda data processing pattern I use as a workaround for this very problem. It involves creating single-row helper tables that store outer CurrentValue values into cells, so that they’re accessible in nested Filters and FormulaMap loops. I call this pattern Iterator tables, and beside being a workaround for CurrentValue, these are very powerful for doing more complicated calculations The video i…

I have built that for you in your doc. You can see it under the Connor Solution page:

This is an issue that coda is aware of, see this post from shishir: Outer CurrentValue access - #48 by shishir

That said, in this case I don’t think you should need this functionality if your doc is representative of your actual use case. You’ll be better off making a table called, “Orders” where you order one product at a time, and then you can batch those by clicking the “order” button which will assign all of them the same order id.

[J_Pi]

Dear @Connor_McCormick,

Thanks for the guidelines and @Paul_Danyliuk, thanks setting up the explanation.

Good to understand that Coda is working on it