[6.1] Journal Items Difference btw. GTK and Web, Web doesn't work - no Counterpart Item created

Bug #1020929 reported by conexus - s.petersen
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Odoo Web (MOVED TO GITHUB)
Status tracked in Trunk
6.1
Confirmed
Medium
OpenERP Publisher's Warranty Team
Trunk
Invalid
Medium
Unassigned

Bug Description

Hello

we already reported this for 6.0 several months ago:
https://bugs.launchpad.net/openobject-addons/+bug/834512

In 6.1 it's still there.

New Database with Demo Data and Generic Chart of Accounts.

Open Journal Items, select the Sales Journal (EUR) and click on Search and then New.
Enter the Partner Axelor, Name = test, Debit: 1000

GTK:
hit Enter, the Counterpart Line is created.
Save, the Tax Line is created

Web:
hit Enter, an new Empty Line is created.

So the manual creation of Journal Items only works well in the GTK Client, it's not useable in the Web Client since 6.0.

Please check!

with kind regards,
Sven Petersen

Tags: maintenance
Revision history for this message
conexus - s.petersen (s.petersen) wrote :
Revision history for this message
conexus - s.petersen (s.petersen) wrote :
Revision history for this message
conexus - s.petersen (s.petersen) wrote :
Revision history for this message
conexus - s.petersen (s.petersen) wrote :

Hello,

today, after the Runbot Version of 6.1 is online again, I tried to check it with current builds.

Build: 13021
Server: 4229
Addons: 6876
Web: 2392

Now the Period in Journal Items is always readonly.
Why was readonly=True added to the field definition in Revision 5366?

Revision 5366 of account.move.line

- 'period_id': fields.many2one('account.period', 'Period', required=True, select=2),

+ 'period_id': fields.related('move_id', 'period_id', string='Period', type='many2one', relation='account.period', required=True, select=True, readonly=True,
                                store = {
                                    'account.move': (_get_move_lines, ['period_id'], 20)
                                }),

Now it's as far as I can tell not possible at all to manually create Journal Items? Please explain!
Please check with the current build!

thanks!

Revision history for this message
Amit Parik (amit-parik) wrote :

Hello,

It's working fine with trunk, So I am assigning this on OPW due to blocking point on stable 6.1.

Thanks!

summary: - 6.1 Journal Items Difference btw. GTK and Web, Web doesn't work - no
+ [6.1] Journal Items Difference btw. GTK and Web, Web doesn't work - no
Counterpart Item created
Changed in openerp-web:
assignee: nobody → OpenERP Publisher's Warranty Team (openerp-opw)
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
conexus - s.petersen (s.petersen) wrote :

Hello,

Thank you for the confirmation.

On the latest trunk version I get an

"Encoding error
No period found or more than one period found for the given date."

when trying to save a Journal Item through the Web Client, although a period according to the date has been automatically retrieved. See attached Image.

Thank you!

Revision history for this message
conexus - s.petersen (s.petersen) wrote :

Hello,

in current Trunk Build 17841, the above noted error is gone, however after hitting enter only an empty line is created, no counterpart line - so it's like described in the first post.

Thanks

tags: added: maintenance
Revision history for this message
conexus - s.petersen (s.petersen) wrote :

This has been set as invalid for trunk, why?

In current trunk (build 22651) neither posting through Journal Items nor Journal Entries create Counterpart Lines!

Revision history for this message
conexus - s.petersen (s.petersen) wrote :

Hello,

almost a half year later it's still not solved.

In today Runbot Build 4862, I'm still getting the Error in the Journal Items List View:

"Encoding error
No period found or more than one period found for the given date."

Nobody does manual accounting neither with 6.1s Web Client nor in v7?

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.