Hey @JonL, What did you end up doing for this as a workaround?
I recently switched over a new project clone to use a PG database and after setting it all up in Wappler the PK increment ID fields are screwing up all by INSERT queries.
They were defined as Increments in Wappler but created as INT4 32 characters in Postgres and then have nextval('departments_id_seq'::regclass) in the defaults section of that field.
I think i figured it out. Looks like Wappler did change it as per your linked suggestion.
The problem is that i imported a bunch of demo data that already had values in the ID fields. When creating a new ID, postgres thinks to start back at 1, and there is already a 1 in the ID field etc.