I have created a 1:1 relation using row id.
I get some related records but most are blank and when I filter the Sheet data with a row id key value that returns no related data in the relation it is there in the Sheet data source.
In order to rule out some effect of row id I also created a second relation using a separate unique key. Same result.
Note the first row id key value shows no related record
However, that key value has a record in the related table (see inset in red frame).
I am a free account newbie so I’m confident I am doing something dumb but:
I have searched pretty thoroughly.
I am not using row ownership or any visibility logic.
I have checked the limits on the free account and can find no mention of relations
Can you provide some additional screen shots please:
One that shows how your relation column is configured
One that shows your first table, including the column headings
One that shows your second table, including the column headings and with at least one non-matching row visible
Basically, I want to first see that your relation is correctly configured, and then see enough that it’s clear there are non-matching rows where there should be.
I struggled with this because the data editor only shows 25 rows of the related table, none of which match on the screen shot I made of the first table. Glide allocated row ids to all rows so I think it is not truncating the data. Perhaps we could solve this wrinkle first?
I can’t find any obvious reason why it would show on 25 rows in the data editor. The 25th and 26th row both unremarkable.
However, it does explain the other problem. The only relations that returned data were in the first 25 rows of the related table. Clearly glide thinks the data stops at row 25. Is there a table config somewhere that shows the extent of the table Glide sees?
No, but it is limited by the type of plan you are on. The Free Plan, for example, is limited to 500 rows.
I still haven’t actually seen anything in your screen shots that shows rows not being matched that should be, so I’m not 100% convinced that it isn’t working as expected.
Just a couple more questions:
How is the Aphorism column in your first table populated?
Are Glide Tables your only data source, or are you also using another external data source? (Actually, from your very first screen shot it looks like you have a Google Spreadsheet connected?)
Commitments table and Aphorisms table were originally related with a foreign key in Commitments.
I understood that I’d be better off using row id if I wanted unique keys generated by Glide so I created a row id column for the Aphorism table. I then did a vlookup in the Google Sheet to map the original FK to the row id. I pasted the values I got into the Commitments.Aphorishsm column. I did another Vlookup to test that I had the right mapping (subsequently deleted). When I realised I had a problem I used the original FK for a second relation column that demonstrated the same problem. I am now convinced that the relations are returning nothing because Glide can’t see beyond 25 rows in the Aphorism column. I checked and all the relations that worked correctly are in those 25 rows.
Google Sheet is the main source of data but there is one Glide table generated by Glide, Users.
I understand the row limitations for free accounts but that’s per table, yes
It’s the end of my workday here in the UK so I’m going to think some more and hope inspiration strikes me.
Thanks to @Darren_Murphy for his help and advice and @david for his confirmation.
I deleted a bunch of rows to get under the limit and confirmed this was the problem but I saw no obvious warning or error. My fault for misreading the conditions of the free tier.
