[trunk][account_cancel] error when saving journal settings

Bug #657247 reported by Ruud Riem-Vis
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Released
Medium
OpenERP R&D Addons Team 3

Bug Description

Having the module account_cancel installed, first create one supplier invoice and do the payment.
Now select "Accounting->Configuration->Financial Accounting->Accounts->Journals" and then open the "Expenses Journal" for editing.
Do not change anything and click "Save".
You'll get the message "You cannot modify company of this journal as its related record exist in Entry Lines".
If you do the same with a journal without any entry, you do not get the message.

This bug blocks from modifying the journal settings if you already have some entries in it. Therefore, you cannot change the settings for allowing canceling entries for example.

Thanks.

Revision history for this message
JMA(Open ERP) (jma-openerp) wrote :

Hello Ruud Riem-Vis,

It's not a bug but just a warning !

It seems you are trying to modify the journal which still has moves lines associated to it.

i.e. You cannot change the company associated with the journal if there are corresponding entires.

'Allow cancelling entries' field, if set to true it allows user to cancel entries & invoices.

Thank you.

Revision history for this message
Ruud Riem-Vis (ruud-riem-vis) wrote : Re: [Bug 657247] Re: [trunk][account_cancel] error when saving journal settings

  On 12.10.2010 08:57, JMA(Open ERP) wrote:
> Hello Ruud Riem-Vis,
>
> It's not a bug but just a warning !
>
> It seems you are trying to modify the journal which still has moves
> lines associated to it.
>
> i.e. You cannot change the company associated with the journal if there
> are corresponding entires.
>
> 'Allow cancelling entries' field, if set to true it allows user to
> cancel entries& invoices.
>
> Thank you.
>
Hi JMA,

I know that the message is a warning and that you need to enable 'allow
cancelling entries' to remove the move.
But the problem is that you cannot enable it because it gives you the
message when you try to change it!
Even if you do not modify the journal settings and press save you get
the same message. Please read the bug decription carefully again.

So I'm in a kind of a deadlock where I want to enable the journal
modification but I cannot change the journal settings because there
already exists an entry. Furthermore, I did not change any company, I
only try to save the journal settings itself in order to by able to
change the journal entries afterwards.

Please tell me if you understand the issue now.

Thanks,

Ruud

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hi Ruud,

How do you pay the invoice?

Thanks.

Revision history for this message
Ruud Riem-Vis (ruud-riem-vis) wrote :

  On 12.10.2010 20:48, Jay (OpenERP) wrote:
> Hi Ruud,
>
> How do you pay the invoice?
>
> Thanks.
>
I've paid the invoice the normal way, i.e. "Pay Invoice" from the
invoice form view.
Ruud

Revision history for this message
Leigh Willard (leigh) wrote :

I get the same error but in a different place. I open up the account using the menu:
accounting / configuration / accounts/ accounts

and choose an account, (make no change) then click SAVE.

The message comes up:

you cannot modify Company of account as its related record exists in Entry lines.

all that I want to do is change some minor configuration of my account.

(and the warning message is bizarre, doen't make any sense - bad grammar)

Revision history for this message
Ruud Riem-Vis (ruud-riem-vis) wrote : Re: [Bug 657247] Re: [trunk][account_cancel] error when saving journal settings

  On 13.10.2010 15:49, Ruud Riem-Vis wrote:
> On 12.10.2010 20:48, Jay (OpenERP) wrote:
>> Hi Ruud,
>>
>> How do you pay the invoice?
>>
>> Thanks.
>>
> I've paid the invoice the normal way, i.e. "Pay Invoice" from the
> invoice form view.
> Ruud
>
Hi Jay,

If it helps you, I can send you the database in a private mail. It is
rather small and only contains the sales entry which causes the problem
in the journal.

Just let me know.

BR,

Ruud

Changed in openobject-addons:
assignee: nobody → RME(OpenERP) (rme-openerp)
Revision history for this message
Ravindra Mekhiya(OpenERP) (rme-openerp) wrote :

Hello Rudd and Leigh,

I had followed your steps to reproduce that warning message but it wok quite well.

Would you please try with latest ?

Let me know if it's still problem at your end.

Thanks.

Changed in openobject-addons:
milestone: none → 6.0
Revision history for this message
Vinay Rana (OpenERP) (vra-openerp) wrote :

Hello Leigh Willard,

The warning message is only come when you will change the company of the journal which contains other company journal entries.I did not face this warning at any other possible scenario as you specified in the bug.
So currently I am closing this bug and you can reopen this in future if you will face similar problem again with proper steps.

Thanks,

Changed in openobject-addons:
assignee: RME(OpenERP) (rme-openerp) → nobody
status: New → Invalid
Revision history for this message
Leigh Willard (leigh) wrote : Re: [Bug 657247] Re: [trunk][account_cancel] error when saving journal settings

I just did another test. When I use the GTK client I am able to make a
minor change, but using the WEB client I always get the error. Did you
do your test using the GTK client or the WEB client? I guess that when
you do a save using the WEB client that it is ALWAYS passing the company
name into the save routine, even if the company name has not changes.

Please confirm.

Thank you,
Leigh Willard

On 10-11-02 05:02 AM, vra (openerp) wrote:
> Hello Leigh Willard,
>
> The warning message is only come when you will change the company of the journal which contains other company journal entries.I did not face this warning at any other possible scenario as you specified in the bug.
> So currently I am closing this bug and you can reopen this in future if you will face similar problem again with proper steps.
>
> Thanks,
>
>
> ** Changed in: openobject-addons
> Status: New => Invalid
>
> ** Changed in: openobject-addons
> Assignee: RME(OpenERP) (rme-openerp) => (unassigned)
>
>

--
--------------------------------------------------------------------------------
Leigh Willard, BSc, MSc Leigh Willard, BSc, MSc
Director, Business Solutions Directrice, solutions d'affaires
telephone: (418) 780-1815 #226 téléphone: (418) 780-1815 #226

                            skype: agil-it.com
                          http://www.epsilon-ti.com
                           <email address hidden>
--------------------------------------------------------------------------------

Leigh Willard (leigh)
Changed in openobject-addons:
status: Invalid → Confirmed
affects: openobject-addons → openobject-client-web
Changed in openobject-client-web:
assignee: nobody → OpenERP SA's Web Client R&D (openerp-dev-web)
importance: Undecided → Medium
milestone: 6.0 → none
Revision history for this message
Jiten (OpenERP) (jiten-openerp) wrote :

Hello,

This bug issue is solved by attached patch.
And It needs some changes from addons side.

Thanks.

Revision history for this message
Jiten (OpenERP) (jiten-openerp) wrote :
affects: openobject-client-web → openobject-addons
Changed in openobject-addons:
assignee: OpenERP SA's Web Client R&D (openerp-dev-web) → OpenERP R&D Addons Team 3 (openerp-dev-addons3)
Changed in openobject-addons:
milestone: none → 6.0-rc2
Changed in openobject-addons:
status: Confirmed → In Progress
Revision history for this message
Meera Trambadia (OpenERP) (mtr-openerp) wrote :

Hello All,

We have fixed the problem in Addons3 branch. The problem was related to bug https://bugs.launchpad.net/openobject-addons/+bug/681272 and we have applied patch in Addons3 given by Salvi Angjeli.

revision-id: mra@mra-laptop-20101214110437-dflw8j6sn3cys097
revno: 4718
branch-nick: trunk-dev-addons3

So i make this bug fix released now.

Thanks all for your contributions.

Regards,
MTR

Changed in openobject-addons:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.