OK, I misunderstood your request. You can first create a relationship from table A to table B and the column usc that you want to copy to table b. Then, you can add an “on submit” action to your column in table b.
If you cannot establish a relationship between table A and table B, what if you start from table B instead of table A? In other words, table A becomes the destination.
Another way is to fill it into the user table first. This method is usually easy to grab the value back to place it anywhere.
I think maybe for the progressive columns in table B can be moved to table A. This might reduce complexity. Your choice component can still fetch its value from table A.
I still don’t understand the problem here. If you only need to add a value to a column in table B everytime a row is added to table A, you can just have an “Add Row” action to table B?
By requirement is There is a Text Entry in my UI, When user enters some string there only in that case it should write the value to column in Table B.
its a only if case when user enters text in that input.
Not every time user will choose to input in that field.
Also to give you more context, Table B has all my choice values written in each column. I use around 10 Choice fields and each of the values of choice fields are being fetched from Table B. So writing a row I dont think will work in my case.
