In the Netherlands it is customary for small
businesses to configure the Chart of Accounts
with 4-digits account codes.
This scheme is broken when several accounts share
the same 4-digit prefix, which was the case before,
as the truncated codes will not be unique.
Fixes#13853Closes#14175
The default background-size for the s_big_message snippet was not
set to "cover" as the "oe_img_bg" class is missing from the snippet
structure. As this change is not critical but should not be merged
in a stable version, this change will be done in master and this
10.0 fix will only force the "cover" value for the default bg thanks
to LESS.
Commit 19e3757ffb allows to return the product price without the
discount included in the unit price. However, `lst_price` is always in
the company currency, not in the pricelist currency.
opw-692896
The s_parallax snippet was refactored in 10.0 but this refactoring
broke some snippet extensions such as the s_parallax_slider.
This made the texts disappear once the snippet was resized.
This reverts commit 6d9c59f348.
This commit is breaking the enterprise/master branch because the method _get_delivery_methods takes 5 seconds to be executed with some delivery methods. Now, instead of having 1 delivery method displayed, the admin has all the delivery methods in order to be able to publish/unpublish them. As this method is called for each carrier, the phatom js tour takes more than 15 seconds to display the page /shop/confirm_order in the ecommerce, with is more than the timeout threshold.
I revert this commit while waiting to find a proper solution.
If a PO with picking is canceled, then reset to draft and confirmed again
two pickings are created. Indeed when creating the picking, moves related
to the PO are confirmed and assigned, even those which were previously
canceled.
This commit ensures that canceled and done moves stay in their state.
This avoid having two pickings for a single PO.
When there are 3 different lots reserved for 3 different serial
numbers for the final product, if you do the first finished product, the
finished lot is put on all stock.move.lots even if nothing has been
consumed for it.
This results in traceability report for the first finished lot being linked
to all of lots instead of just the one that was consumed.
Now we update lot_produced_id only on stock.move.lots where quantity_done > 0.
That way it will only links with the correct one.
Some banks, like ING, create a line for free charges.
We just skip those lines as there's a 'non-zero' constraint
on the amount of account.bank.statement.line
After modifying the database schema, if some models do not have a table/view,
attempt to recreate it by calling their method `init()`, following inter-model
dependencies.
Fix the model `board.board` by making it an abstract model.
Add the missing model dependencies on report `crm.partner.report.assign` to make
it depend on report `account.invoice.report`.
Push and procurement rules are some difficult concepts to understand.
Add some tooltips :
Push Rules tooltip :
When a move is foreseen to a location, the push rule will automatically create a move to a next location after. This is mainly only needed when creating manual operations e.g. 2/3 step manual purchase order or 2/3 step finished product manual manufacturing order. In other cases, it is important to use pull rules where you know where you are going based on a demand.
Procurement Rules :
The demand represented by a procurement from e.g. a sale order, a reordering rule, another move, ... needs to be solved by applying a procurement rule. Depending on the action on the procurement rule, this triggers a purchase order, manufacturing order or another move. This way we create chains in the reverse order from the endpoint with the original demand to the starting point. That way, it is always known where we need to go and that is why they are preferred over push rules.
overwrite in the context was never passed to update_translations
Loading the translations with the overwrite checked did not overwrite the
previous translations
Introduced at d465346
normal mode: Importing only regular/basic fields from source file
advanced mode: Importing any related fields from source file(i.e. if detected pattern in header like '<relational_fieldname>/<fname>')
- Rename following checkbox "Show all fields for completion (advanced)" in "Show fields of relation fields (advanced)"
- If the import file contains a column with a field of a relation field, show the column label in the preview, even if "Show fields of relation fields (advanced)" is not checked > to make it less confusing when importing advanced files (e.g. products with attributes)
Purpose:
On a list view (Ex: the invoices list view), if a column is a currency column (Ex: total amount), it makes no sense to display the aggregate (Ex: sum) if the records contains several currencies.
Spec:
Don't display the aggregate of a column if a least two records are in different currencies.
The tests are running on consumable product, it means that there is no
resevation of quants and verification of reserved quants when you create
and assign moves. So the tests are not really usefull with consumable
products.
To make the tests efficients, we set the products as stockable. And we
use 'reserved_availability' instead of 'availability' in tests
'test_10_pickings_transfer_with_different_uom' and in
'test_00_picking_create_and_transfer_quantity' be cause the assert is
done after the move reservation.
In test 'test_00_picking_create_and_transfer_quantity' when we check the
move_lines state after the action assign, the first and last should be
only 'confirmed, because they are partially available. When product
were not stockable, all lines were assign, because there was no check of
the reserved quants.
In 'test_10_pickings_transfer_with_different_uom' we removed the call
'picking_out.action_confirm()' and 'picking_out.action_assign()',
because they already have been called before.
The price set for the non integrated carrier must be the same either when you
set it on the SO with button "set_price" or when you set it on the stock picking.
The field "carrier_price" must be in readonly when the state of the picking is done.
opw:691224
When a column holds more than 40 records tooltip indicates 40/<record_number>.
However this is not really helping. What is interesting is the total number
of records.
If multiple views had the same name and same priority, the order
of application of their xpath was not deterministic. That may be a
big deal if both of them were doing xpath with position = inside.
Yannick Tivisse