Look-up of look-up - only populated after record updated in Noloco

I’m sure this has been reported before, but only could find a similar issue but slightly different. So reporting here, apologies if duplication.

I have records being created via Xano API. I have noticed that sometimes, and can’t see a pattern, where I’m using lookups of lookups, they do not get populated until I manually update the record in Noloco.

I use these look-up fields for permissions, so causing some issues as you might imagine. Any help hugely appreciated, can provide examples etc. Thanks!

1 Like

Just an FYI, I’m still seeing this issue and it has to somehow be related to the order that records are being added to my database.

So I have 2nr video records, each linked to a submission record. The submission record is used for the look-up value.

When the first video arrives, the submission is not populated, but instead added a little later, which seems to make the lookup function correctly. When the second video arrives, the submission exists when the record is created, and then the lookup doesn’t seem to work. I guess it’s because the first scenario has an update, which in turn fetches the look-up. Or something like that anyway!

Hey Luke, thanks for sharing this context.

Youv’e seen this pattern repeatably?

If so, that might help us figure out what’s happening

It’s really hard to see the pattern because the data in being synced in from Xano, so it’s often hard for me to see the order it is being synced into the database, not sure if this is strictly in timestamp order, or whether it batches. But I’ll keep testing and see if I can somehow isolate.

You’ll see in the below grab though that the “client” field is a look-up from submission. Most of them not populated for some reason, and this is what I use for permissions! In the submission record, all the client data in the records is populated, but these are once again looked-up from another field. So it definitely seems to be when the look-up source is a look-up itself.

But if I manually update any of those records from the grab, then refresh, the client look-up works.

I hope that all makes sense!

@carlos @darragh

I’m still having issues with this unfortunately. After looking at it in more detail, it seems that when the record is synced across from Xano, but no further updates are made to the record (either manually or via sync), the look-up of look-up doesn’t work.

Any help on this would be hugely appreciated, otherwise I’ll have to work out how to force re-sync somehow after initial sync is completed, which I’m not 100% sure will work.

Thanks!

Not sure if this is the right thread to ask about this in but I’m seeing lookups of linked tables not populating unless I remove the lookup and add it back.

Yep, exactly the same for me! Very much hoping a fix can be rolled out for this soon as causing me all sorts of issues!

I think it has something to do with the direction of the link but since I’m building right now I keep moving things around and cant say that for certain - using make.com and some conditional logic as a work around

@darragh @carlos Morning! Really sorry to chase on this one but just wanted to check if on the radar? I can follow another route by adding my linked fields directly to avoid look-ups, just don’t want to do this if not necessary! Many thanks in advance :pray:

Hi @lukebranford - it’s something we have on our list, but because it’s due to the intricacies of syncing, we haven’t been able to reliably reproduce the problem.

It’s something we hope to tackle in the next few weeks.

Thanks for your patience here.

1 Like

@darragh That’s great, thanks for the speedy reply, much appreciated. I’ll put a temporary workaround in place in the meantime.

1 Like

Out of curiosity are you running into issues replicating it on the Noloco Table side as well?

We haven’t seen the issue on Noloco tables, but I see your message now @SamEdwardsRVA

Could you send us those details - we’re putting more engineering work into this soon

1 Like

We have some good news - we identified and fixed the issue with lookups of linked fields.

As you described @lukebranford and @SamEdwardsRVA , they were not updating correctly. We rolled this out on Friday afternoon, so it would be great to understand if any changes to lookup values after that have been applied consistently, of if there is anything else we need to look at.

Thanks again for flagging this and working with us to get to the bottom of this complicated issue.

1 Like