New Bug Encountered: ref pulls wrong column

[Olivia_Bryanne1]

Hi there,

I’ve linked two tables and made a form for the second so that once the ref field is set by the user using a dropdown menu the other fields in the form will autopopulate. The ref works fine and pulls the right entry, but the autopopulated values to not correspond to the right columns - e.g. the field Name pulls the parent entry’s email address instead. It’s the right row, just the wrong column

Any suggestions?

Olivia

[Aleksi]

Please check that your label column is set correctly in your ref (parent) table.

[Olivia_Bryanne1]

Not sure I get this, the label on the child table is the timestamp value. Should it be any different?

[Aleksi]

I wrote it wrongly. You need to check the label column from the parent table, not from the child table. Sorry about the typo. When you choose the parent record from the ref dropdown, you will see values from the label column. When you save the record, it will save the key column’s value though into your database.

[Olivia_Bryanne1]

ahh now I see. Yes the label shows correctly in the dropdown and the entry that is pulled is correct. It is the columns that are not correct. I.e. the app formula [ref].[name] gives me the value of the [ref].[email] column

Also, its not like its shifted systematically by e.g. 2 columns. One field pulls the column to the right of what it should be and the other just says NAN because the column type is a number and its pulling a text value

[Dengue_Evaluati]

Adding to what Aleksi said, AppSheet displays the label of the referenced table but the value recorded in the database is still the key to that table.

[Aleksi · Accepted solution]

It sounds that you have two different app versions where it’s saving the data in a wrong order.

[Olivia_Bryanne1]

yes this was the case. I had an old version of the parent table as a read-only in the app. Regenerating the structure did the trick. thanks a lot!

[Aleksi]

You’re welcome