For the reference field on the right side of the relationship, change that field to be a formula numeric field. Then make the formula the field which has the Record ID# of the source table. It probably has the field name [Record ID#2]
Okay, so the tables are DNT and Network Operations. In the Network Operations Quickbase I connected table 1 from the DNT quickbase via a quickbase synced table. In the Network Operations table that I synced from the DNT quickbase, I added two new fields and I need to push them back to table 1 in the DNT quickbase.
Qrew LegendWell, you could create a cross app relationship where one Network Operations has many DNT. You will need to make this relationship starting from the Child side, so from DNT.
This will end up connecting those two apps in the same Quickbase process so if you have a large amount of users in a large amount of data than it could affect performance. Once you have that relationship you can look up any fields from Quickbase operations back into DNT
We did that but it did not give the options on which field to connect to. We could do the lookup but how do we tell it record id on the DNT table matched record id2 on the Network Operations table. When we let it do it's own connection, it wasn't bringing back the data.
Qrew LegendFor the reference field on the right side of the relationship, change that field to be a formula numeric field. Then make the formula the field which has the Record ID# of the source table. It probably has the field name [Record ID#2]
Okay. I knew there was a trick, I just could not remember how. Question, you mentioned possible performance issues. Is there something I should look at to determine if we might run into issues? If so, would there be a work around, like maybe a pipeline? The Network Operations QuickBase has 283 active users. Of course not all of them are in it 24/7. I'm not sure of the number of users on the DNT but I could find out.
