Hereโs some context. My app is about sheep. The table Iโm in, โTop Level Dataโ, has many records where each row is a record of a sheep and each column is different attributes of the sheep. The label for each row is the โTagโ of the sheep and each has a unique ID for a key. The particular column in the app iโm interested in is a dropdown menu where you can select the โsireโ or father for the sheep record. The โsireโ value is just going to be another sheep/record from the same table. For that reason this โsireโ column is listed as a โrefโ type with no formula and the referenced table is the same table, โTop Level Dataโ.
How I expected it to work was that when adding a new sheep record I could click the โsireโ dropdown in the app, select a sheep by its tag/label and the source/table/spreadsheet would populate on the back-end with the key related to that row referenced. This way, when someone is looking at a sheeps record at a later date they could click on the โsireโ listed and it would redirect them to that record.
That is ALMOST whatโs happening. For whatever reason, in the app, when you go to add a record and you click the sire column, you CAN select any of the โtagsโ/labels for any sheep in the table HOWEVER in the back end the source table/sheet is populating with that โtagโ/label value rather than the key. So itโs not linking to anything.
Im confused about this because as far as I understand, when you have a column designated as a ref column it utilizes the label for app selection but it ACTUALLY populates with the key for that table. Why is that not happening here? Did I misconfigure something or is it a bug?
LinkedIn
Twitter
