Forum Discussion
QuickBaseCoachD
9 years agoQrew Captain
I suggest that you make the 2nd field for related customer be a formula equal to the first Related customer field.
A safe way to do this, assuming that you are dealing with a Production app and do not want to accidentally break it, would be to create the new field called something like [Related Customer mirror] with a formula of [related customer]. Then pull in a few lookup fields to confirm it it working ok.
Once you are satisfied that it will work OK, then you can go to the field for [Related Customer 2] (or whatever it is called) and change the field type to be a formula field and have the formal be [Related customer].
A safe way to do this, assuming that you are dealing with a Production app and do not want to accidentally break it, would be to create the new field called something like [Related Customer mirror] with a formula of [related customer]. Then pull in a few lookup fields to confirm it it working ok.
Once you are satisfied that it will work OK, then you can go to the field for [Related Customer 2] (or whatever it is called) and change the field type to be a formula field and have the formal be [Related customer].
CaroleVandenbe1
8 years agoQrew Cadet
Sadly, I cannot find where I did this before successfully but cannot get it to work again. Questions: is it the reference proxy I need to change to a formula field that matches the contents or the actual numeric reference field? If I use numeric reference, it doesn't pull any data - but i'm thinking those internal numbers don't match and that's why. But if I change the text reference proxy to a formula, it pulls it out of the relationship. Works but doesn't allow for any lookups.