emre1e

i found the issue. On the file https://github.com/nocodb/nocodb/blob/08d73677dc6e794babe930edd8b54e2dc465434f/packages/nocodb/src/lib/models/ProjectUser.ts#L79-L94 The order by clause missing. If im right it should be something like: const queryBuilder = ncMeta .knex(MetaTable.USERS).**orderBy(`${MetaTable.USERS}.id`)** .select( `${MetaTable.USERS}.id`, `${MetaTable.USERS}.email`, `${MetaTable.USERS}.invite_token`,...

I think this is an issue in the roles & rights. If you create a filter with the Creator Role, then users with the editor role cant see the filter...

"Gericht": [ { "Name": "xxxxxx", "Land": "xxxxx", "Strasse": "xxxxx", "PLZ": "99999", "Ort": "Test" }, { "Name": "xxxxx", "String": "xxxxx", "Land": "xxxxx", "Date": "2021-01-26", "Strasse": "xxxxx", "PLZ": "99999", "Ort": "Test" }...

Update: This happens only if this field also Exists in a lookup column and if its NULL. Error Field "Aktenzeichen_Musterentscheidung" is missing in the list. Its only available as lookup...

@dstala i dont think this bug is fixed. Even with the newest daily docker image, im getting the same response from api. ?nested[Gericht][fields]=Gericht_Name,Datum_Musterentscheidung "Gericht": [ { "Gericht_Name": "Amtsgericht Eschwege" }...

can we please fix this. Please make the fields shown in the api even if the lookup field exists and the value is NULL.

If i go with == "" its not working with null values. Only for empty strings. null is recognized by nocodb so its not invalid. You can also use null...

even in the sql its not working. Maybe its because of postgresql. if you excecute this in PSQL you will see the duplicated entries. Just change the offset. 14 Users...

you see the user id repeating. Its default behaviour if you offset a table without primary key. You need a order by to work.   

Just look first one and last one. there are many duplicated. Its default behaviour on tables without primary tables. If i put in a order by clause, everything starts to...