The image of an alternative product must be centered and the name
of the product must be cut with "..." if it's too long for the block
to keep the symetry for each block.
opw:647612
When converting an invoice in journal entries,
the invoice lines amounts must be currency rounded
not only when the invoice currency is different
than the company invoice,
but also when they are the same.
Otherwise, a rounding issue can happen
if the `Account` decimal accuracy is greater
than the currency rounding, the journal entries
total and the invoice total could be different.
e.g.
- Set decimal accuracy of Account and product to 4
- Create a supplier invoice, any supplier
- Add a line as follow:
- Product: None
- Quantity: 2057
- Price unit: 11.9150
- Tax: 16% (create a new tax with 0.16 as percentage)
- Validate the invoice
- In the other information tab of the invoice,
click on the journal entry
- Notice that the first line has as credit amount 28430.6150
While the invoice total is 28430.6200
- Now if you try to create a bank statement with one line
of -28430.6200 and as partner the supplier you chose
in the second step of this explanation, and try
to reconciliate it to the invoice created above,
the above won't be marked as paid, while it should.
opw-647639
Fixes#8135
for some fields, the value is an array with the value and a description. In that
case, we need to only take the value in account to set the id of the group.
If there is no partner on the contract to which are invoiced
the timesheets, the error telling you to set a partner (and a pricelist)
must be raised before trying to create the invoice, not before
creating the lines of the invoice.
In this case, this is because if you set no customer
on the contract, there is no pricelist automatically filled
as well, and the currency is took from the pricelist,
which will be False in the case there is no pricelist
on the contract, and you cannot create an invoice
with no currency set.
opw-647672
- Don't show the button 'Validate' of the statement form when there is no statement line
- In reconciliation widget, use term 'Validate' instead of 'Register Payment' for the use case where the transaction is not reconciled on the spot
Elements in a .o_row are displayed like if they are .oe_inline
elements but div elements also needed to be inline-blocks elements
and to have space between them.
The string belongs to the account module, but was wrongly added to
stock.pot. This commit adds it to account.pot, but also keeps it for the
moment in stock.pot to prevent losing existing translations in
Transifex.
This causes issues when people delete the Website Sales team. The
website_sale module already adds a salesteam_id to website, which is
configurable. So instead set that to website.salesteam_website_sales by
default and use this field.
Modified version of afc9507 after 8c31ecd:
website_crm doesn't look for the website_sale salesteam anymore
The custom filters were not translated in the user language(FR) when:
-Going to Marketing / Mass mailing
-Creating a new one
-Selecting "customers"
-Clicking "select records"
-In the modal, clicking Filtres / Add custom filter
To have the user_context, the context sent to fields_get must be taken
with get_context.
opw:647495
In the standard account_analytic_account module,
the employees have the read access to the analytic accounts.
Therefore, it makes sense to give the read access to the
account distribution plan, so an employee can choose one
in a purchase order when the Analytic Accounts for Purchases
is activated.
opw-647606
When the Purchase analytic plans module is not installed,
the analytic account field in the lines of the purchase order
is available only for the group
`Analytic Accounting for Purchases`
It should be the same for the field of the analytic distribution plan.
Otherwise, it will lead to an access error if you don't, as
you do not have access to the required model.
opw-647606
when grouping selection fields, the drag and droe was broken (it looked like it
worked, but the id was not saved properly). The problem was that the column id was
not saved in the group.
Another problem was that the creation of new columns was possible when grouping
on non many2one fields
Goffin Simon