I might be able to manually rehydrate them over the weekend, we don’t have that functionality at the moment, but I would be surprised if that didn’t fix them
If possible, would you be able to test if they work correctly by creating a copy of one of the ones that currently doesn’t work?
Great idea, I just created a copy and it works.
If you could rehydrate them on your end, that would save a lot of time. Let me know if this is an option.
Thanks for your help.
This should be something we’re able to do over the weekend.
If you have a list of the different lookups that need recalculating, I can do that.
If there’s an order of operations that would also help - i.e. if Lookup B depends on Lookup A, I’ll need to re-do Lookup A first
Hey Darragh, I sent you a DM on Friday. Thanks for helping out.
These have been refreshed - hopefully this means they’re all up to date now
Appears to have worked. Thank you so much!
Happy to help! Thanks for your patience @fundmore
@darragh I’m still having an issue where lookups of lookups are not auto-refreshing. Simply, the issue is:
If I have a value, and a Lookup A which references that value, and a Lookup B which references Lookup A:
When the value changes, Lookup A is updating. But the change in Lookup A does not trigger an update in Lookup B.
Here’s a specific example:
The Deal’s Closers field links to Emanuel, the Submission’s Closers field inherits that, but the Offer’s Closers field is blank.
The Offer’s Closers field is a lookup that should be inheriting its associated Submission’s Closers field (which in turn is inherited from the Deal’s Closers field).
Hi, I’m having the same problem: a lookup of lookup is not always refreshing. From time to time it does, from time to time ti doesn’t…
I’m happy to share details if need be.
Thanks!
Hey @Polka it would be great if you could share some detail in a DM here or in the chat and we can investigate this further for you
Thanks
Sorry, I changed so many things since then that I don’t have a clear example anymore. I’ll share something if the issue arises again 
Thanks @Polka - just let us know when we can help
I’m still seeing that lookups don’t refresh when the source field is updated:
Deal #12854 has two Originators: Mark and Robert.
Submission #51645 has a Deal field that’s linked to Deal #12854.
And Submission #51645 has an Originator field that’s supposed to look up Deal #12854 and inherit its Originators.
But the Originator field on Submission #51645 only has one Originator, Mark - it does not have Robert.
So the lookup is not being refreshed when the Originators field of Deal #12854 is updated.
On a practical level, this means that when someone reassigns a Deal to someone else, the new assignee will be able to see the Deal itself but not any of the Deal’s Submissions, Offers, etc.
This because their permissions are set up so that they can only see records whose Originators field contains them.
The Deal table has the actual Originators column which the user directly updates. But the downstream records all rely on a lookup to the Deal’s Originators column.
Since the Originators field of these downstream records isn’t being updated, they are blocked via permissions from the newly assigned user.
Are there no plans to make lookups composable? @darragh
Hi @fundmore - thanks for your patience here.
We have confirmed that lookups of lookups work without issues on Noloco tables, the problem is related to the nuance of synced tables.
The team are actively investigating it though. We’ll keep you updated with our progress.
Thanks again for your patience
Thanks for the update. I have only been using Noloco tables, not synced tables.
I’ll let you know if the issue persists. Thank you.
Hi @darragh - I’m still running into the same issue.
This is a case where the Originators on a Deal were updated to include an additional user.
Deal #18200 (Originators: Max, Jacob)
↓
Submission #68038 (Originators: Max, Jacob)
↓
Offer #7499 (Originators: Max)
You can see that the Offer did not inherit the additional user, Jacob, in its Originators lookup field.
Hi @fundmore
We have some good news - we identified and fixed the issue with lookups of linked fields.
They were indeed 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.
Excellent, thanks @darragh and team, much appreciated! I’ll test later and let you know if I have any issues.
Thank you so much for addressing this!