You can use (and adapt to’m your context) the following filterbyformula formula to filter your list :
And(Search(, {Field}) = 1, LEN() = LEN({Field}))
So that you’ll get only the results matching your search parameter. If your value to search is “Ryan”, length = 4 and you’ll get only results with Ryan, if any.
Add the Lower fonction suggested by @karimoo, it’s an excellent idea!
I was expecting this to work, but it didn’t. It is a combination of the search you’ve shown plus a user filter that was working before I added the and() formula. Have you had many problems with ands… what looks wrong with my formula?
I think I know what you mean, but that would involve a lot of coding in Airtable.
With what I’m thinking, I would be able to save searches and filters, but it’s going to be another project.
On second thought, what I’m imagining won’t work unless lists within lists are working properly with Airtable formula filters.
@bgschust Just one more guess. What if you add two filters in Adalo . One for the Search and a second for the user id. Never tried it with Airtable. But two filters in Adalo are combined with an AND.
Could you please clarify? I built this previously with Adalo bases, but then I switched to Airtable because I needed more analytical and review power. It is not practical to switch everything again in a short amount of time.
There could be a ghost haunting my app development environment.
I can’t get the user filter to work with the exact same formula I had before. Somehow I lost ground. I can’t get the user’s record fields in the formulas now. This happened before, then started working, and now it doesn’t again.
There’s something going wrong with how values are passed from text input fields and Airtable record properties back into Airtable inconsistently.
There have been days where input fields and Airtable-source dynamic text both work, but now today, the dynamic text is not working. It was working earlier yesterday. If the quotes are causing issues, that would explain why I can’t even get the User ID to match today without even bringing AND() back into it.
I am able to get formulas to work in Airtable, but the problem arises when I apply them through Adalo. Could Custom Actions be modified to enable list retrieval from Airtable?
@jeremy know it’s a big ask, but if you’d be willing to share more screenshots about how Adalo’s back-end works, maybe I could help diagnose the problem there. My interface is too limiting at the moment. You guys can see everything I do, so I feel like it’s fair.
If someone could teach me how to use Postman, I think I could do a lot. I just don’t know how to use it yet. I have it downloaded.
@bgschust 1. When you say something is broken, what has been working before:
Did you make any changes to the table in Airtable?
You might need to refresh / reconnect the table again.
What is the field type of User ID in airtable? A Single line text or a Link to another record?
What I found out in the meantime:
If you use filterByFormula on a Link to another record type, you must send the value for the primary key of the linked record (in simple words the value you see in Airtable) NOT the id in airtable.
Can you use the Java Script Console in Chrome?
Is there any HTTP error showing up? E.g. HTTP 422 indicates that there is a problem with a field type.
If you want me to screenshare with you, I can do that.
I think we need an Adalo employee to help because I don’t know how else it’s going to get fixed.
The only thing I changed was trying to add a second filter with the and() function. When I gave up on that and decided to go back to just filtering on user, now it doesn’t work unless I put the user into a text input field first. But then someone could change their username in the textbox so that is not a good solution. It was working without that workaround just yesterday.
That’s certainly another important issue. I’ve been working around it with custom modals that have lists of items to select as a replacement for dropdowns. It’s tedious but it works for now.
With the filter issue, I don’t see a reasonable way around it unless I try to use conditional visibility on multiple layers of groups. It’s hard to say whether that’s a reasonable approach.
Being able to apply MULTIPLE CONDITIONAL VISIBILITY parameters would solve the problem, and/or enable the option to add and remove components from a group.