I’m migrating an existing membership onto an app I built in Softr. There are about 600 member records in Airtable, assigned to various statuses (Active, Set to Cancel, Cancelled, and Payment Failed/Removed). Of those, about half of the members are “Active” or “Set to Cancel”, and those two groups are the only members who will have any access on the new site (further divided into user groups based on “Annual” or “Monthly” membership status). I haven’t had any trouble setting that up.
My issue: I’m getting ready to migrate everyone tomorrow by sending invitations via Softr, but I can’t figure out a way to exclude the non-active members from the invite without manually going in and selecting users based on user groups (it seems we can’t even sort by user group).
There are 2 easy options for you (form my understanding of your dilemma).
set up different filter views in Airtable. Then select your view as the data source for users within softr. this way, softr will only create users that are in the correct filter view within airtable.
create conditional logic for your user within softr. For example, if status=active, user is created or is assigned a user role etc.
My issue was that I had already connected a table that wasn’t filtered, and the popup I got in Softr when I went to disconnect/reconnect the data source made it seem like the users that had already been recognized weren’t going to be removed.
I then tried filtering with Softr (see the screenshot below), but it didn’t work well retroactively.
I ultimately did the work manually because I needed to get the invitations out over the weekend. That turned out to be glitchy, too - we’ve been fielding lots of “I cancelled this membership 5 months ago” types of emails - but at least it’s done.
My recommendation to anyone finding this thread in the future? If you’ve already connected to an unfiltered table, consider duplicating the entire app and connecting to a filtered table rather than trying to fix the issue after the fact.
