It's no more possible to set CLP to pointers in version 2.1.0

[SebC99]

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!

• You're running version >=1.0.23 of Parse Dashboard.

• You're running version >=2.3.2 of Parse Server.

• You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

With last version (2.1.0) of the dashboard, it's no more possible to set CLP to pointers as when we choose one of the pointer suggested in the list, nothing happens, and the row is not updated

Logs/Trace

No error concerning this issue in the console (just a Uncaught TypeError: Cannot read property 'current' of undefined at IntersectionObserver.<anonymous> (dashboard.bundle.js:95) which does not seems related

[mess-lelouch]

@SebC99 I could be wrong, but last time I checked it was possible to set pointer CLPs. I think you just have to press Enter once you select the pointer on the dropdown list. Let me know if that helps.

[difelice]

I think class_permissions schema was updated on Server:

Server 3.10.0

{
  "class_permissions": {
  "get": { "user": true },
  "find": { "user": true },
  "count": { "user": true },
  "create": {},
  "update": {},
  "delete": {},
  "addField": {},
  "protectedFields": { "*": [] }
}

Server 4.3.0

{
  "class_permissions": {
  "get": { "pointerFields": ["user"] },
  "find": { "pointerFields": ["user"] },
  "count": { "pointerFields": ["user"] },
  "create": {},
  "update": {},
  "delete": {},
  "addField": {},
  "protectedFields": { "*": [] }
}

Ref: parse-community/parse-server#6352

[henrikperrochon]

Hi,

I am also facing issues with the pointer / array of pointer CLP edition on parse dashboard.

Adding an authorization for a specific pointer would add the field name of the pointer in the readUserFields in previous version (first screenshot) ; now it adds the field name in the action (get, find, etc. second screenshot). It looks like more granular but it simply does not work.

I've been reading the source code and it does handle readUserFields here (https://github.com/parse-community/parse-server/blob/27832453e292ab9f1c607d115939a9f35f3fb373/src/Controllers/SchemaController.js#L1357) but I cannot see where the new Schema with the pointer's field name set inside the operation (get, find) is used?

[mtrezza]

@henrikperrochon, @SebC99 could you verify whether this issue still occurs with the latest alpha version?