V11 User Permission Redesign Issue

Hello, everybody!

I discovered, one critical bug in ERPNext v11, that turns the system unusable!

We have create a new Role, and refined the full permissions for that Role, after that we have used the fixtures to sync the permissions, and during the migration process, we discovered that all permissions are tecnically gone.

Tecnically because, the record of the permission is into the database, and into the repository, but as you can see into the image below, there’s no field for directly relation between Custom DocPerm and the DocType itself, so, it means that Frappe is using one of the restricted fields eg: (parent, parenttype, parentfield) to store that information, but with that behavior, when we reimport using fixtures, everything is set as null, because ERPNext dont export that information into the fixture system.

Also, it turns the system unusable, because we dont have ways to migrate, and keep updating the system, because we know, pemissions will be lost.

@umairsy, We want to start using the hours to fix that issue.

@bern-lefebvre

[KanchanChauhan]

@MaxMorais We had a similar issue, on every migrate custom permissions disappeared. But I am not sure if it a bug or just not a correct way of exporting permissions.

We changed our way of exporting permissions and it works fine now. We just set permissions and use this to export permissions and it works like a charm.

[umairsy]

@MaxMorais request you to post this (and future) queries on [e-mail], where we give support to our paid customers. It will help us escalate to the concerned person.