I’ve experienced this issue in varying degrees since I started with Noloco last year. About 50% of the time it seems to work mostly fine and the other 50% is either minor glitches or larger ones like the video.
Video
I have a collection of receipts that are attached to a project. Once they are uploaded they get matched up with a corresponding cost line in the budget. I do this via a receipt collection in a tab of the project page. It’s much easier to have the cost line selection via in line edit as opposed to modal or clicking into a record but its very unreliable. Typically the drop down will close while you’re trying to search and you have to attempt it 2-3 times. Then, the linked record once selected will disappear after a few seconds.
Here’s what the edit log looks like in airtable:
Hey @onlymatt thanks for flagging this
For what it’s worth, the change likely does work the first time, it’s just not updated in time
We’re going to improve the loading state here which I think would give everyone better visibility of what’s still loading or not
If this is a crucial workflow I’d probably recommend switching to an action button or something more deterministic
After looking at it closer, it does fill about 90-95% of the time and just isn’t reflected on the page without a refresh (and waiting a bit). There are still some times it doesn’t stick. FWIW, I added a button to the record to see if its more stable but the results are the same.
And it’s only an issue with this status field @onlymatt ?
Is there anything unusual about that field? It’s not dynamic or formula driven in any way?
Not formula driven. The list to choose from is filtered by another linked record (Project) but that aspect is working fine. It also allows multiple linked records to be selected so potentially that is where some of the instability comes from? I have noticed a similar issue in the past with selecting project managers which is another linked record field that allows linking multiple.
Are we not takling about a single-option field @onlymatt ?
Could you send me a link to the field that’s having problems in the Noloco data table and I’ll double check there’s no naming conflicts
