I have a form called Costs that is always assigned a linked record of a project. I’ve been using this same form since I began with noloco last year. The project value has always been hidden on the form and its auto filled based on which project a user initiates the form from. I’ve just realized that just about 2 weeks ago it stopped filling the hidden value for project. I changed the form so that “project” is not hidden and it functioned correctly but after changing it back to hidden its not working. To my knowledge I haven’t changed anything that would impact this. Please help?
Hey @onlymatt - taking a look at your setup, I see that your costs table has permissions setup.
What user roles are creating costs records? Have you confirmed they have permission to ‘Create’ on the ‘Project’ field?
It was myself (admin) it was happening to. I was able to resolve it a few minutes ago with some additional manual syncs.
I’m experiencing the same issue with the same modal form today. I’ve tried syncing everything I can think of. The button in question is action 5 on this page as an example. It’s set to autofill “Project” as hidden based on the row value but isn’t filling again. The native add record button on this collection is set up exactly the same way and working fine.
Hey @onlymatt - we’re just catching up on some tickets here, is this still an issue for you?
Which button should I be looking at on that page
Its currently working again
I’m experiencing this again with a different form on the same page. The previous form was a record button. This one is the main collection page form (https://app.mintconstruction.com/costs/new). It’s supposed to fill the project value as a hidden field but has failed 2/2 times this morning. I even changed the form to display a section if the project field has an empty project value and it doesn’t show. I’m sure this is a syncing issue as things like this happen regularly when I make airtable field additions or updates. I run syncs on affected collections regularly and so far have run 3-4 sync this morning to no effect. As with previous times it will start working randomly at some point. I really need noloco to stay in sync better with airtable, its far too easy to break with minor updates. Is there something else I should be doing on my end?
Hi @onlymatt where is it supposed to fill that value?
IF you navigate DIRECTLY to that page, then there’s no hidden value:
c
Are you opening the form from a project page perhaps? In that case it shouldn’t be to do with syncing
Both the main form and the button in reference are used from a project page like this. The form I had trouble with yesterday has been the same setup since I started with noloco last year and that’s the first trouble I recall, but the button has been intermittent at other times.
Assuming you always click the ‘+ Add’ button, and the user that’s clicking it has access to create records and fill in the ‘Project’ field, then it should always work
You can see the value passing forward in the URL here:
If you dont’ go to the form via the ‘+ Add’ button on the page you linked me, then there’s no guarantee there will be a value for ‘Project’ in fact it will likely be empty
Correct, I always use the +Add button including this instance that I’m referring to. It is working again after several syncs but seems to reliably break if I add fields to airtable and doesn’t necessarily fix with manual syncs initially. At times it takes several manual syncs of all involved collections. I’ve gotten in the habit of manually syncing collections after I’ve made airtable updates and generally that cuts down on the issues but not always. Still, I would hope to not have to manual sync all collections on the backend whenever I make updates just to prevent issues.
Based on what you’re describing, I don’t understand how syncing can play into it, unless I’m misunderstanding.
When you visit that form from the Project, the ID of the project is either there or it’s not, right?
It should always be there if you’re coming from the project page. There’s nothing to be synced
Maybe help me understand how you’re thinking about this
I created a record from the project page using the +add form button. The linked record field for “Project” was not filled as it should be, it was empty so the record would not display on the project page since it was unlinked to the project. I have a view in airtable for records with missing project field, that’s where i found it and manually added the project to correct it. That view currently has 6 records in it from the past few weeks where I didn’t notice the project field wasn’t filling and I can’t figure out which project they should go with. About 4-5 other records I was able to manually fill. Perhaps the best thing to do it not manually fill the record next time and I can provide you a link to the record ID?
The reason I suspect syncing is because I had a similar issue several times when I started with noloco where the “personnel” field was supposed to be filled in the same manner of a different form and was glitching. I had to contact support a few times and for help and found that syncing after airtable updates would help avoid the issues.
Thanks for the context matt, my only conclusion really is that sometimes the New page is visited directly, without coming from the project.
Maybe you could make it a non-hidden field and make it required?
That way it will still prefil
It would at least make it more obvious if it for some reason doesn’t fill in
I’ll share specifics if it comes up again. I’ve made myself and automated email for any records created without a project so that I can catch it quickly.
@darragh it happened about an hour ago with the same form which was accessed via the collection add record button on this page of the project. Here’s the affected record. I had to manually add the project in airtable to keep my team working but here’s the revision history.
I changed it to a visible field that’s required for now because of how disruptive it is when this occurs but really don’t prefer it that way
If you can spot when it doesn’t show up, please let me know.
We haven’t seen anything like this before, and so long as the value is in the URL, and the user has permission to write to that field, then it should be there.
Except maybe if they somehow open the form too quickly or something