User Groups not working with postgres

Data Sources
1

I recently changed from Airtable to Postgres.
I built the same tables with the same name on Postgres that I had on Airtable.
I have some User Groups that are based on table rules.
Now, after the airtable switch to postgres, the rules are not being read correctly and the users are being classified to the wrong user group.
As you can see I have this user classified with 3 user groups (no batch, no assistant, no team)

image
image1133×222 25.3 KB

But in the user group rules, to be classified they gotta to have this on their table

image
image665×818 32.9 KB

However, look at my table on postgres

image
image1370×253 20.2 KB

The raw is empty on the three of them.

If I mark as true, nothing happens

I tried to delete the User Group Rule and create the same one again but it doesnt change the end result

2

Can you pls add support[at]softr.io as a collaborator to your app and DM me the app link then I will check it and see what’s wrong… I guess I need to see what’s the data-type under that checkbox

3

Done.

You can check now

4

@elementttt can you pls DM me the app url too ?

5

App url or database url?

6

app url would be fine

7

Check your dm

8

check your dm please

9

Still working on this @elementttt

Sorry for the delay.

10

ok! because this is really important, please take a look asap

11

@elementttt as this is a boolean field with checkbox please use true or false values.

I fixed one of your conditions pls follow the same approach.

Screenshot 2024-07-20 at 23.23.06
Screenshot 2024-07-20 at 23.23.06980×642 30 KB

1 Like
12

thank you!

Fixed

On airtable I was using field not empty to refer as true boolean. On postgres it is supposed to use true

1 Like
13

What if you have a users table in airtable but are migrating to Postgres? How does this all work?

14

Thanks its working now!

15

@aar0n you can have many datasources and the app still will work if connected right. Users could come from AT or Postgres and as long as you have a way to do the filtering e.g. if users are in AT then in Postgres you might need to have a User email next your data or ID

1 Like