When you create a Ref column, whether itโs a โstandardโ Ref column or used with the โIs a part ofโ setting, AppSheet will ALWAYS automatically generate a REF_ROWS column list in the table being referenced. REF_ROWS is the function used to generate the list of rows from the related table. That column name will start with the word โRelatedโ + โname of column referencingโ and then a letter โsโ is tacked on at the end.
This explains the last column listed in your column list - โRelated Customised Combo Roman Blindsโ.
The other two columns MUST have been created manually. This could be either by renaming the automatically generated column or just straight out creating the column.
For example, after setting up the REF column, AppSheet would have automatically created the column named โRelated Customised Combo Roman Blindsโ. If you changed that name to simply โCustomised Combo Roman Blindsโ, then on the next table generation, AppSheet will automatically re-create the โRelated Customised Combo Roman Blindsโ column and you will have both columns present in that referenced table.
The question isโฆ Do all three of these columns generate the same list of REF rows? If they do then DELETE the first two Virtual columns from that Parent table and leave the โRelatedโ column - the one that is automatically generated. Use that column in your views
If it is the case the that โRelatedโ column doesnโt provide the list of REF rows you need then by all means add your own custom column of REF rows. Youโll need to decide which of those other two coumns is the one you wish to keep and delete one not needed. This does mean that both, your manual column and the automatic โRelatedโ column, will need to be left in the table. If you have no need at all for the โRelatedโ column, then hide it by turning off Show? property.
LinkedIn
Twitter
