I want to use a choice component in the edit form to allow users to change the status of their order. The status column is a single select field. I applied filters to it to only show certain options. However, in the glideapp, the field now shows up as a text field (with the A icon) and displays only the first option for users to choose (when it should be showing three options). This was working before, so I don’t know what happened.
I set containers to only show under certain conditions. However, when I test the glideapp, I can see the containers when I shouldn’t and I only see some fields in those containers (other fields in those containers are missing).
I made a text and set it to show only under certain conditions but it is showing regardless.
Here is an image of the filter conditions for one of the containers. The conditions are the same for all the containers - essentially, I only want them to show if the user’s order status isn’t Picked Up or No Showed, as that would mean that their order is past and can no longer be changed.
I suspect the problem may have to do with the fact that glideapp seems to be treating single select fields in airtable as text fields, so having the same root cause as problem #1.
As for problem #3, nevermind! It’s working now Maybe it takes glideapp a few hours to reflect changes correctly? I have noticed that.
This isn’t correct logic for your filter. The way you have it configured, if the status is ‘Picked Up’, it still fits the filter that the status is not ‘No Showed’. Likewise, if the status is ‘No Showed’, it still fits the filter that the status is not ‘Picked Up’. You need to change it from an OR to an AND because you want to filter statuses that are Not ‘Picked Up’ AND Not ‘No Showed’ When you use an OR like that any status is going to fit no matter what.
Ugg, I’m not an expert on how these things work with Airtable. Normally I would have a separate table that lists all of the status options in separate rows. That separate table would be the source table for the choice component, and then your choice component would write the value to your form destination table. That logic makes sense to me.
But it seems that Airtable lets you have different column types that serve dual purposes. In this case, it contains the list of options as well as holds the value of the selected choice. If I’m understanding correctly, you are trying to use the same column as both your source and your destination, and that doesn’t play well with glide.
This is similar to Linked Records that hold the value for a relation as well as serve as the relation. Glide has some workarounds in place to handle these types of Airtable columns but I’d say it’s not standard procedure to set things up like this.
I think in your case, you can get away with it as long as you create a separate table with all of your choices, and then use that as your choice component source.