[6.1] Error trying to create periods using Web Client
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Odoo Addons (MOVED TO GITHUB) |
Fix Committed
|
Medium
|
OpenERP Publisher's Warranty Team |
Bug Description
Getting a problem with trying to add a periods to a newly created financial year in web client.
I was able to create a new period successfully in GTK client however.
If I then return to web client and call up the period under "Config/Financial Accounting/
Unknown field state in domain [["state"
I can successfully view/edit in Config/Financial Accounting/
All of the above works fine in GTK client.
I did this on a fresh install, no sample data, and no default chart etc installed.
Related branches
- Rifakat Husen (OpenERP) (community): Approve on 2012-06-08
-
Diff: 36 lines (+4/-3)1 file modifiedaccount/account_view.xml (+4/-3)
Changed in openobject-addons: | |
status: | New → Incomplete |
tozm (tozm) wrote : | #2 |
Thanks for that. I can see a an important difference between what you see and what I see.
When I select the financial years form, in order to create one, I don't have the field displaying for "Company". (Is this because I only have one company configured?) This may be a red herring.
But I copied your steps and that worked fine if I create the periods using the create periods button. But as soon as I select one of those periods by clicking on its link *on that same form*, then I get the error referred to above:
Unknown field state in domain [["state"
This is the one step that you didn't do in your video... so you haven't yet actually performed the step yet that triggers my problem.
Note that viewing/editing the periods in the periods form works fine.
Thanks for your prompt feedback - look forward to an update when you have a chance to try this again.
Hello,
I have faced the problem of "Unknown field state in domain [["state"
Thanks!
Changed in openerp-web: | |
status: | Incomplete → Confirmed |
assignee: | nobody → OpenERP R&D Web Team (openerp-dev-web) |
importance: | Undecided → Low |
tozm (tozm) wrote : | #5 |
Thanks. Glad you could reproduce it.
Changed in openerp-web: | |
status: | Confirmed → Incomplete |
status: | Incomplete → Invalid |
status: | Invalid → Incomplete |
Hello,
As per the comment#4 video, It's produced with following revision number.
web : 2293
server : 4130
addons : 6715
That's why I am again confirming this issue.
Thanks!
Changed in openerp-web: | |
status: | Incomplete → Confirmed |
This bug happens to me too.
The same way that Amit.
Changed in openerp-web: | |
importance: | Low → Medium |
affects: | openerp-web → openobject-addons |
Changed in openobject-addons: | |
assignee: | OpenERP R&D Web Team (openerp-dev-web) → nobody |
Hello Guys,
As far as the web is concerned, its necessary to have the state field in the view when the other fields depend on it.
See the .py file and make sure the other fields like date_* depend for their readonly status on state.
Hence, the attached branch will do the rest.
Though its in 6.1, I understand that it should go fixed.
Regards,
Bipin Rathod,
Serpent Consulting Services.
Thanks for the fix Bipin, a good catch.
I am setting the bug as fixed committed, but I let OpenERP Team decide who to assign to(either SerpentCS or team).
I am sure this bug will give a sigh of relief to the affected ones.
Thanks,
Serpent Consulting Services.
Changed in openobject-addons: | |
status: | Confirmed → Fix Committed |
milestone: | none → 6.1 |
Changed in openobject-addons: | |
status: | Fix Committed → Confirmed |
status: | Confirmed → Fix Committed |
Hello,
I have faced the same problem in 6.1 as well as trunk also. So it's will be fix for trunk and backport from the trunk for 6.1.
Thanks!
Changed in openobject-addons: | |
assignee: | nobody → OpenERP R&D Addons Team 3 (openerp-dev-addons3) |
If this is gonna be in 6.1, its best thing to do Amit, good decision.
Thanks,
Serpent Consulting Services.
Changed in openobject-addons: | |
assignee: | OpenERP R&D Addons Team 3 (openerp-dev-addons3) → OpenERP Publisher's Warranty Team (openerp-opw) |
no longer affects: | therp-backports |
Dears,
This was a blocking point for many in 6.1. This merge was approved too.
Hope to get this noticed.
Thanks.
I am effected by this bug.. Is the fix for this bug merged ??
Muhammad,
The fix is attached already.
If you have an OPW, you may get this quickly merged.
Thanks.
Hello tozm,
I have tested your Issue in web-client, But I did not face any problem. It's working fine at my end. I have attached the video for your reference. Would you please check it and notify us where you have faced the problem.
Thanks and waiting for your reply!