The object ir.filters has no security rules. anyone can access and
delete other people rules.
Add several rules:
- The administrators have all the rights on ir_filters
- An employee can create/modify a filter for him or everyone. But not for someone else
- An employee can delete only delete the filters he created
- A portal/public user can only access the filters for which he's the user
When a user goes through the trouble of manually modifying the
depreciation lines he will lose all his work when clicking on 'reset to
draft'. Furthermore, if he then goes through the trouble of repairing
the problem by once again manually changing the depreciation lines he
will again lose his work when pressing confirm.
opw-678678
Used case:
Create a SO with invoicing policy based on delivery. Don't deliver
anything and Create invoice for all invoiceable lines.
Result:
There was no invoice created and no warning message.
After the fix:
A warning message is raised when after clicking "Create
invoice",for any reason it doesn't create an invoice.
opw:678567
The field generation is most of the time following the pattern
`field_<table name>_<field name>`
but in case of name clash (e.g. res.partner.category - id and res.partner -
category_id), the id of ir.model.field is added at the end of the external id
during the field creation.
The more flexible way to link to an ir.model.field is to use the syntax
`search=[('model', '=', <model>), ('name', '=', <field name>)]`
to avoid errors as in #12192 when the "first" external id no longer exists.
Fixes#12192Closes#12198
In the sales receipts :
- In Sales Receipts : Change the String Date into Bill Date
- Always display the Journal Items tab
- In the Journal Items tab : Display the date. the string should be Accounting Date
- In draft : There should be an onchange on the accounting date when the bill date is changed
- In draft : It should be possible to change indenpendently the accounting date
- The entries should be posted at the accounting date
In the purchase receipts :
- Always display the Journal Items tab
- In the Journal Items tab : Change the string Date into Accounting Date
- In draft : There should be an onchange on the accounting date when the bill date is changed
- In draft : It should be possible to change indenpendently the accounting date
- The entries should be posted at the accounting date
Contrary to other payment acquirers all transactions through stripe are
s2s transactions. Because of this payment_stripe has to create it's own
payment.transactions which is unusual.
Because of this payment_stripe needs a sale order id which will be
provided by website_sale in request.session. website_quote doesn't do
this so this extracts it from the return_url, just like
website_quotation.js does.
opw-678117
The attendance module needs to know if the user is an employee before
putting itself in the systray. This commit add the information in the
session infos, and use it directly.
This commit introduces a mechanism to add information into the session
from a different module, without having to fetch it manually with a rpc.
This is intended to be used with small pieces of info required at the
start of the web client, such as currency informations.
To add information to the session, one can simply inherit from ir.http
and modify the session_info method.
By default, when reading a m2m field, entries that are
deactivated in the destination table are not included.
This behavior is desirable in some cases (e.g. for
"tags" or "categories", but not for entries that
significantly impact other field values in the parent
record, such as taxes.
The problem is rather obvious: when displaying a
paid invoice that used taxes that are now deactivated,
the taxes are hidden while they still affect the
computed amount. And after cancelling + resetting
to draft, the tax is not taken into account anymore,
while still being linked.
Forcing the field-level (python) domain to include
both active and inactive entries solves the problem:
- when reading, displaying and recomputing values,
deactivated taxes will be included.
- when trying to pick a tax, deactivated entries
will still be ignored, as expected.
This commit applies the technique to all m2m
fields that refer to taxes.
Fixes#12066
opw-677751
This particular report was broken for a long time. Instead of fixing it
it was removed because the use case for it is unclear and noone seems to
actually be using it anyway.
There is no way to directly create restaurant.table records in the
backend. The only way is through adding it directly to the table_ids
one2many on restaurant.floor and when doing that floor_id is
automatically set.
Closes#8705
When using sale_timesheet to create tasks in specific project for certain
products, you should be able to set this setting by company.
Indeed, standard ir_rules prevent you from seeing projects from other
companies; therefore it makes little sense to have this field set to
the same value for all companies.
Symptoms: running a full reconciliation manually with that wizard was resulting in not fully reconciled aml altough the total in company currency and in secondary currency were perfectly matched. Full use case described in added test test_manual_reconcile_wizard_opw678153.
Problems:
- The system was processing by pair of aml and creating exchange rate entry/full reconciliation as soon as possible whereas in that case it needs to be postponed at the end of the manual reconciliation otherwise some entries would be excluded from processing.
- Another problem was that because of this batch processing, we ended with unconsistent amount_residual_currency values for some entries that were fully reconciled in company currency but not in foreign currency (also negative amount_residual_currency for a debit line which should never happens)... To solve that, we now process the manual full reconciliation in two steps: only in company currency first, then in secondary currency if needed. A small adaptation in the payment widget of invoices was needed for that too.
Darshan Kalola