Daily updates from Odoo
Friday, September 4, 2015
4 changes · master
Resolved issues and error corrections
Creating a contact from a partner form could fail when returning to the contact card view if some card fields were not available from the form. This fix prevents that error by safely handling missing field values, making contact creation smoother for users.
Original PR description
…partner. Issue ID: 647856 If we have an internal kanban view and an internal form view defined for an O2M field and if the fields that are used(which checks for field value using raw_value) in…
…partner. Issue ID: 647856 If we have an internal kanban view and an internal form view defined for an O2M field and if the fields that are used(which checks for field value using raw_value) in kanban-box isn't defined in it's respective internal form view then it would lead to an error(when switching from form view to kanban view at the time of record creation) as shown in below screenshot  Here, a similar situation arises with res.partner's child_ids(Contact) o2m field in res.partner.form view. The internal kanban view is defined with fields "image, color, is_company, fax" but these fields aren't defined in internal form view. So, when we create a contact(switch to internal form view) and then click on "Save & Close"(ie, switching to kanban view), it couldn't find the fields that were defined in kanban view and hence resulting in the error as show in screenshot. I tried to fix this issue by setting default false to such fields. Would you please have a look at the fix. Thanks.
This fix ensures invoices created from a Point of Sale order form show the correct total amount. It helps businesses avoid billing discrepancies and keeps POS accounting records accurate.
Original PR description
… invoice from pos order form Issue : 646664
The recruitment applicant form now correctly creates an employee without triggering an error. This prevents disruption for HR users when converting successful applicants into employees.
Original PR description
… Employee button is clicked from applicant's form view, also removed api.model as this method doesn't need decoration Issue: 647286 _broadcast_welcome method is defined in hr.applicant but while migrating this module to new api it is called with employee recordset(Either we should mode this file to employee model or keep it in hr.applicant itself and pass employee object as a argument, I keep it in hr.applicant itself as there is no other use of this method except posting new message when employee is created from applicant.)
Fixes a crash that occurred when users clicked the New Node button in the Diagram View for lead automation campaigns. This helps users continue building campaign flows without interruption or client-side errors.
Original PR description
Issue : 643191 Steps to reproduce: - Lead Automation -> Campaigns -> Click on "Diagram View" -> now click on "New Node" button. - It gives client error... snap --->>> https://goo.gl/4x0tpS