I have Table A with a select list column. Then I have Table B where there is a relation column where I connect Table A and I add the select list column there.
My problem is that in Table B I cannot change the connected select list column even is I switch on two-way edit in the relation column.
Is it somehow possible to be able to change the select list in Table B so it changes also in Table A?
Table A
Table B
Thanks!
Hello @Tamas_Mahner ,
It is really hard to understand what you are trying to do if you don’t share a sample document with the community - screenprints don’t give us any insight in your formulas or column types.
Table B has Application in it’s name. but shows an interested party. How did this record end in your table B? What are you trying to change - and into what?
Many things are possible, but we need to know what you want.
Greetings, Joost
You are right, sorry!
Basically what I would like to do is to change the Table A “Level” column in Table B.
I connect Table A with a simple relation column to Table B, I add the “Level” column in Table B and then I would like that I can change the level in Table B so it also changes in Table A.
Here you can find the doc:
I hope it is clearer now.
Thanks a lot!
Hello @Tamas_Mahner ,
I am sorry to say that with the sample provided, I am not going to be able to help you.
You put a bunch of ccc type entries in the columns, but that does not really give me an idea of what you are trying to accomplish.
It is not clear where the entries for table come from: do you make new rows by hand, what is the function of table B, are there going to be many more rows in table B linked to the same row in table A, or are they all going to be 1 to 1 relations.
Generally speaking, if a column is filled through a formula, you are not going to be able to edit that column, so indeed, it cannot be changed in either table just like that. However, you could change the value with a button (from table B), but keep in mind that any related row (if there are more related rows in table B), will be changed too.
Having said al that, I think table B should be a VIEW of table A, in which case changes in either table will be seen in in the other table.
Another thing is that the activity code should probably come from a activity table (in which case you don’t need the connector column.
The 2-way edit switch has (as far as I know) a different use (I don’t use it, because I just don’t have use for it. It allows you to connect your row to a different row in the source table.
Long answer short: before giving you advise on how to setup your doc, I need a lot more insight into what you are trying to accomplish. Maybe one of the other community members understands it from what you supplied, but I don’t.
Greetings,
Joost
Dear Joost,
I appreciate a lot for your effort and feedback. My approach was to share only the actual challenge I am facing without the context so in case it is something really obvious it is easy to answer and I save time for everyone. 
But it seems it is far more complex than I thought.
In our organisation we implement many projects and activities where we are handling thousands of applications who then becomes hundreds of participants.
Our problem is that we do not have one comprehensive database where we can see ALL the people in one place who we managed to reach out offline and online and then handle their applications separately, connected to the specific project and activity they are applying to.
My idea was to do a three steps registration-application-confirmation system, where we can see in one table all the people who are interested, then we can handle their applications activity by activity. 1 project has 1 coordinator but it can have several activities.
What I established so far:
Project coordinator registers a project and add activities to that project where they will receive registrations and applications. Each activity has a separate application form about motivation, experience, several activitiy specific questions, documents to attach etc.
I created a template with a standard application form, what the coordinators can tailor made, create a form and they copy-paste the link of the application form to the specific activity.
I created a “link generator” table where they just select the activity they want to receive applications and I divided the application process to two steps: 1. Registration, 2. Application to specific activity.
The generated link is a generic registration form what we ask from every single person who applies (name, email address, country of residence) information we always need with a hidden field which tells which activity they are interested in.
This generic form has a hidden pre-filled column with the activity code so we understand from which activity proposal they got the link. They fill in the basic information, the hidden form tells us the actual activity they are interested in and in this way when they submit the registration form I created an automation which sends an automatic email to them with a personalized link to the specific activity.
This is the form what the project coordinator created and tailor made to the specific activity. Motivation, experience, etc. and after submission this lands in a separate table while we have in the registration table each people interested, and in the activity specific table each person applied to a specific activity.
I understand there is the option to simple create table views for each specific activity, however it would not work because in this case for each activity each question will be there and with time it will be overwhelming to go through each time and hide the ones not needed and add the new ones. That table would gradually grow and we do not need motivation and experience in the table where we want to see all interested people, because that would be too heavy.
We are talking about 30-100.000 rows.
So that is why I chose to use a connector which connects the table with all people to the specific activity. At this point the only information I would show in the overall table is the “status” of the person if they applied, selected, rejected which is an activity specific information.
So what I am wondering basically how would it be possible to feedback to the overall table information when the activity specific tables will be definitely duplicates?
I am trying to see if the relation column keeps the setting if I create a template for the activity specific applications. So then the project coordinator just use the template, create a new form, copy the link to the form and then customize the questions whatever is the need of that specific activity.
Does this help a little or confuses more? 
Hey @Tamas_Mahner ,
Well…yes, it explains a bit better what you are trying to do. At the same time, I don’t have a good answer for you. It is going to take me too much time to digest your entire story - now you are talking about projects, activities, links, people, templating and probably a couple more things.
Here is my suggestion if you want to get some help: make sure your table names are descriptive, don’t include things that are not relevant to this question, make sure, if it gets complicated, to describe the process in which way the document will be used.
You sort of did that, but simplified to much.
What you asked for can’t be done directly, but you can make a helper column for a changed level and use a button (or automation) to reflect that change in other tables (use modifyrows() with a filter() )
Let me know if you need help with that (after you clean up your doc and properly name your tables and describe in which table you want this type of button - if that is what you want.
I am not trying to be rude, but if we have to figure out the whole thing, you need consultancy, not help with a function.
Greetings,
Joost
