Community mailing list archives
Re: Record Rules access errorby
Again, I'll try to provide a simple and clean scenario...1- Prepare a new database with warehouse. sales, purchase, and MRP.
2- Create more than one location in the warehouse app.
3- Create more than one user, one for each location.
4- Duplicate the "warehouse user" group, as many locations you created before.
5- Create an appropriate record rule (on stock.moves object), for each of your previously created groups.
6- Create a sales order and some test data to check with.
7- Log in with any user created before.
8- Check ...
(You should SEE the required stock moves as expected, but when you try to Transfer each, you'll get the error in front of your face.)
On Mon, Jul 6, 2015 at 12:03 AM, Abu Helal <firstname.lastname@example.org> wrote:
Ronald, I didn't develop any modules, I just used the core ones besides the record rules to control the warehouse rights.So, I created the above record rules (full privileges) one for each location in my warehouse. Then this error popped up.On Sun, Jul 5, 2015 at 9:47 PM, Ronald Wopereis <email@example.com> wrote:
While writing my own first module, i noticed that "depends" in __openerp__.py somehow triggers an autoload of the underlying model(s) and thereby the load of the access rules.
Hope this helps,
RonOp 2 jul. 2015 07:42 schreef "Abu Helal" <firstname.lastname@example.org>:Hi.(This question is repeated for the second time, hoping be lucky this time)I tried to organize our company's warehouses and locations to the desired structure from our company's point of view to locations such that, (Input, Stock, Packing, and Output).Then I defined a separate record rule for each location, to differentiate between each location moves and the others. Foe a while, everything was going well, but surprisingly, it get a strange error for the storekeeper ..."AccessErrorThe requested operation cannot be completed due to security restrictions. Please contact your system administrator.(Document type: stock.move, Operation: read) "From the first glance I expected that the record rule missed the read permission, but that was wrong. The record rules have the four permissions set!
Can anyone help?