Forum Discussion
QuickBaseCoachD
8 years agoQrew Captain
I see two alternatives.
The first is that if you just want to display information on a child form as an embedded report, then you do not need even a relationship.
You create a Report Link field and set it up so that in the configuration, the two fields match, for example the 6 characters that the user enters compares with a formula field on the VIN table which has a formula such as Right([VIN],6)
However, while you can see the report of the parent VIN record on the child record, those fields are not able to be used in any formuals on on a child report.
The alternative is to use the last 6 characters of the VIN which according to Wikipedia are a unique serials for cars made /in the US https://en.wikipedia.org/wiki/Vehicle_identification_number
as the Key field to the VIN table.
There are two ways to make that happen. One way is to make two formula fields to separate out the parts of the VIN between the serial # portion and the identification / check digit portion. Then change them to text fields and going forward, you will input data in two fields. Then set the Key field to be the serial #.
The other way, is that in fact, you can set the key field of a table to be a formula field, which would allow you to keep your data entry the same, as it may be from some imported source.
If you wanted to do that, I suggest making a copy of your app first and testing you import process after the change is done.
To change the key field to be a formula field is a bit advanced. You would just type the API string right into the URL on your browser along with an app token (or disable app tokens while you do this). https://help.quickbase.com/api-guide/index.html#setkeyfield.html
The first is that if you just want to display information on a child form as an embedded report, then you do not need even a relationship.
You create a Report Link field and set it up so that in the configuration, the two fields match, for example the 6 characters that the user enters compares with a formula field on the VIN table which has a formula such as Right([VIN],6)
However, while you can see the report of the parent VIN record on the child record, those fields are not able to be used in any formuals on on a child report.
The alternative is to use the last 6 characters of the VIN which according to Wikipedia are a unique serials for cars made /in the US https://en.wikipedia.org/wiki/Vehicle_identification_number
as the Key field to the VIN table.
There are two ways to make that happen. One way is to make two formula fields to separate out the parts of the VIN between the serial # portion and the identification / check digit portion. Then change them to text fields and going forward, you will input data in two fields. Then set the Key field to be the serial #.
The other way, is that in fact, you can set the key field of a table to be a formula field, which would allow you to keep your data entry the same, as it may be from some imported source.
If you wanted to do that, I suggest making a copy of your app first and testing you import process after the change is done.
To change the key field to be a formula field is a bit advanced. You would just type the API string right into the URL on your browser along with an app token (or disable app tokens while you do this). https://help.quickbase.com/api-guide/index.html#setkeyfield.html