There’re still problems with the lookup field. It can be solved by recreating the lookup field, but it is so annoying, especially when the website has already gone live.
@darragh , if you are not aware yet, check out our tables. Not sure how to give you the table ID and column ID. This is quite fundamental, hope it can be fixed soon.
ps. we are using Noloco Tables
It seems all those records are created by workflow, not sure if it is related.
Hi @alancui , if you could DM us the link to the table and field which is having issues we an confirm whether it matches what we’re hoping to fix in the next week.
We’ve identified that it’s related to ONE_TO_ONE fields, or when an update is made to the reverse side of the field value
We’re hoping to have more progress in the coming week or two
This is still causing me some issues unfortunately. I have a scenario where I clone a record and all it’s linked records using Xano, but when the data is synced back into Noloco, I have a look-up which stubbornly refuses to work until I manually update any of the data in the record.
We hope to have some improvements in the coming days. We’re doing some final rounds of internal testing
Hey folks - we’ve released a large part of this solution. If someone would be able to confirm if there’s been an improvement to this since Friday?
For any table that’s specifically ‘out of sync’ just reach out to our support team and we can recalculate all the values for you
Awesome, thanks Darragh and team! I’ll reach out to support to get my tables synced then do some testing later today and report back 