Yes, I am facing the same issue now, but it seems that the destination I clicked to select the data relations is correct. However, the column name displayed is incorrect (it shows the name of the last column).
I have observed the same issue. Seems like it started a couple of days ago. Work-around for now is to just move the column that I wish to build the relationship for to the last column position.
Can Glide support please weigh-in and acknowledge the bug has been confirmed and a fix is in the works?
I’m currently facing the same issue, when I clicked to select the data relations it is correct. However, the column name displayed is incorrect. It goes to the last column entry by default and that’s not what I am selecting at all.
I have deleted it, tried again, refresh my page, I also moved the column so, so that the relation will select the last entry in that column, and it did. However, it still did not solve my problem. Is anyone having problems with the look-up as? Does anyone know when this issue will be corrected? I’m also working on a new app and I am new.
I have relation columns set up and working fine. But now when I edit the column the “matches the value in:” field lists fields that don’t match the data that they are returning. I have attached a screenshot that provides an example. the matches value used to point to users > rowID not it displays a nonsensical field yet returns the correct data.
I am experiencing an issue with the relation column in my Glide app. When creating a relation, the system consistently selects the last possible option instead of the column relation I need. This occurs even when I have selected the correct columns and configured the relation settings properly.
I’ve followed several troubleshooting steps, including recreating the relation column and checking for filters or conditions that could be affecting the selection, but the problem persists. I have also confirmed that other users are experiencing a similar issue, indicating that this may be a bug.
Could you please investigate this issue and provide guidance on how to resolve it? Your assistance in resolving this would be greatly appreciated, as it is currently impacting the functionality of my app.
Thank you for your attention to this matter, and I look forward to your response.
Description
Earlier today, one of my Rollup columns was calculated as expected. After a Glide platform update, the Rollup column will only point to the last column in the table.
In screenshot, you can see the Rollup is pointing to Check-in Allowed ITE column when I need it to point to Training Hour Credit column and SUM that column.
Like I said… worked as expected this morning. Came back to it this after to update some data formatting and now it won’t do right.
Same problem - seems to be with rollups and lookups - it all ‘works’ OK but is displayed incorrectly when editing a column. Have logged a ticket (I guess others have too).
Adding to the list of affected users. Having the same issue where all of my relations are only selecting the last column of the table. Existing relations seem to not be affected even though they are showing they are looking at the wrong column, but new relations only let me select the last column and do not work correctly.