is not possible to register new claims

[Admilson Afonso]

Integrity Error

The operation cannot be completed, probably due to the following:
- deletion: you may be trying to delete a record while other records still reference it
- creation/update: a mandatory field is not correctly set

[object with reference: reference - reference]

[Admilson Afonso (admilson2001)]

I'm testing the rev 39, still with the same problem mentioned above

[Maxime Chambreuil (http://www.savoirfairelinux.com) (max3903)]

The fix was committed, but not released.

Please test with rev 40, as I just did the merge.

[Admilson Afonso (admilson2001)]

Will initiate the tests now

2013/4/19 Maxime Chambreuil (http://www.savoirfairelinux.com) <
<email address hidden>>

> The fix was committed, but not released.
>
> Please test with rev 40, as I just did the merge.
>
> ** Changed in: openerp-mgmtsystem
> Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1168584
>
> Title:
> is not possible to register new claims
>
> Status in OpenERP Management System:
> Fix Released
>
> Bug description:
> Integrity Error
>
> The operation cannot be completed, probably due to the following:
> - deletion: you may be trying to delete a record while other records
> still reference it
> - creation/update: a mandatory field is not correctly set
>
> [object with reference: reference - reference]
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openerp-mgmtsystem/+bug/1168584/+subscriptions
>

[Admilson Afonso (admilson2001)]

Just testing rev40, everything worked ok

[Arys Eric (eric-arys)]

Re: [Bug 1168584] Re: is not possible to register new claims

The problem is that the "On change event" on field "reference" use an ir.sequence "mgmtsystem.claim". This ir.sequence is not created by default during the module installation.
For system already install :
-----------------------------------
Just create it in => configuration /sequence to troubleshoot directly.

To fix the bug :
-------------------
The team need to add this data in the default data csv file.