Users may sometimes need to edit their own partner records directly,
although indirect access by writing on `res.users` directly works
fine in most cases.
The SQL view `crm_partner_report_assign`
makes a join on `account_invoice_report`
A column is added to
`account_invoice_report` in the module
`sale` (`section_id` is added to the view),
making the SQL view `account_invoice_report`
replaced automatically at the install/update
of the `sale` module, which leads
to the automatic deletion of the SQL
view `crm_partner_report_assign`,
because the SQL view `account_invoice_report` is
altered.
Therefore, after the install/update of the `sale`
module, the view `crm_partner_report_assign` was
deleted, and the "partnership anaylsis" unusable.
This revision makes sure to init the
`crm.partner.report.assign` report after
every init of the `account.invoice.report`.
opw-674177
List of impacted models:
-account.account
-calendar.event
-crm.lead
-fleet.vehicle
-hr.applicant
-hr.employee
-mail.mass_mailing.campaign
-note.note
-project.task
-res.partner
Add a menuitem in the Configurations for these models, visible in debug mode
For some reason, it was lost. Probably in the graph view/pivot view split.
This commit simply accepts the attribute, but default to true, so nothing
changes unless you have explicitely set it to false.
Also, fixes en error introduced by a forward port (the use of
openerp.web.format_value)
Add a sequence field on the res_company. The companies are ordered
by sequence (by default 10), than by name. That way, we can order the
companies on the company switcher for example, and have the most common
companies first.
- Display the creation date while the order is not confirmed
- Display the confirmation date after confirmation
- Display the expiration date if the order is confirmed
This reverts commit a206114d4c.
This commit breaks several of our long standing and widely appreciated policy
- one commit for one feature; do not forget to put the correct impacted addon
- commit message should explain why the change is performed
- a bug fix in master seems weird, why not in stable. If not applicable to
stable the commit message should explain why
- a bug fix in the ORM should come with a test case
- code is not clean
Following commit 5b380e13, the the taxes on the fees are not calculated
correctly. Moreover, setting the subtotal in the onchange is misleading
since it will be set to zero if the line is not invoiced. We just set
the price to zero by default, and the click on 'update' will set it
correctly afterwards.
opw-673984
This solved two issues. First, the price subtotal should contain the
price with taxes excluded, as it is the case in other modules.
Otherwise, the tax will be computed twice. Then, when an invoice is
generated, the taxes should be calculated...
This is an oversight of commit fe2b5f35a4.
opw-673984
The do_search method still had a race condition because the
read_slice method of datasets alter ids. So, what could happen is
this: a long search is started, then a shorter search is started and
ended before the first search is completed. The ui is rendered
properly, but then the long search ends and alter the dataset. As
a result, the Kanban view is broken (cannot open a record anymore
because the dataset has the wrong ids).
This commit fixes the issue by doing basically what the read_slice
method did, except the ids altering part. However, it introduced
a new problem for x2many kanban views: these kanban view don't have
the same dataset, they have a datasetstatic. The naive substitution
does not work, so I had to reintroduce the old method in X2ManyKanbanView.
ON THE DELIVERY SLIP :
1. CUSTOMER REFERENCE
- If a customer reference is filled in the SO, on the delivery slip, under
Customer Address, add a section Customer Reference :
- Display every customer information in the header
2. SO NUMBER
- Display the SO reference under the origin instead on the picking type name.
Do not display it if unset
3. LOCATIONS AND STATUS
- remove the columns locations and status
4. ORDERED QUANTITY
- add a column (between product and quantity) named Ordered Quantity. It
contains the quantity of the initial demand. Rename Quantity into
Delivered Quantity
5. BACKORDER
- If the delivery is a backorder, add the string : This shipment is a backorder
of "stock.picking.name".
- If a backorder has been created, add the string : All items couldn't be shipped,
the remaining ones will be shipped as soon as they become available.
- If it is a backorder and another backorder has been created, both strings should
be printed.
6. SCHEDULE DATE
- Should be the date when the delivery order is validated.
- Rename Scheduled Date into "Date"
- If the DO is not yet validated, display the scheduled date.
- If the DO is validated : display the date it was validated.
7. WEIGHT
- Add the unit of measure after the weight value
- Display only if set
8. CARRIER
- Display only if set
9. LOT/SERIAL NUMBERS
- Keep the header of the column + rename it into Serial Number / Lot
10. CUSTOMER/CONTACT ADDRESS
- Should be displayed on the right, keep only minimal information: Customer name,
phone number
ON THE PICKING REPORT
- picking: https://drive.google.com/file/d/0Bx4JWs1efCreX1FrZUhaZDEtblU/view?usp=drivesdk
- form: https://drive.google.com/a/openerp.com/file/d/0B5BDHVRYo-q5X3VGVWI1aThWcWM/view?usp=drivesdk
Olivier Dony