You should check the settings of the Region collection and make sure that you include the ‘id#primary’ field
1 Like
I don’t know why, but ‘id#primary’ was off.
Thanks for not dropping it).
It remains to be solved why the tables cannot be linked, but that’s another story and a question for Supabase.) 
@luka Hi Luka, I am having the same issue, but everything seems to be set up correctly.
I have a product DB & a subcategory DB linked related with a “subcat_id”, but the lookup does not return anything and also has an error for the first parameter.
I know these databases are linked correctly because it works in a Bubble app that uses the same database via an API.
Any ideas?
You are missing subcat_id key in your lookup formula, it should be:
lookup(item.data.subcat_id, subcategories.data, "subcat_id")
then you do
getKeyValue( your whole lookup, "subcategory_name")
Hi Luka.
I still get the same error. Does it make a difference if the id is an int8 and not a text string?
What is the value of Item.data.subcat_id when you have just it in the Formula input?
Can you send me your editor link in private message if the data is not sensitive? I would like to take a look what’s going on here
Thank you , sent
This reply is very useful in understanding the core methods of accessing data in WeWeb.
I vote a version of it should get added to the docs (maybe here) as 1) it should inform how people build and 2) it succinctly introduces several building blocks that will be needed later (db views, local v remote data, realtime, filtering data, lookups, scaling, etc.), providing basic direction for users to research further.
I only found this thread because it was suggested while I was writing a post on advanced collection field configuration!
1 Like
Thanks so much for taking the time to share this with us Daniel, really appreciate it and have passed it on to Matthew who’s handling all things user docs at the moment 