Adding a context which ease budget encoding as really often, creating a budget means the associated budget lines will follow the same start and end dates. Passing the context allow budget lines automatically have the budget's start and end date
Portal users are not allowed to read account.move.line model
Therefore, in the portal, if you let the payments in the invoice view, the portal user is warned that he is not allowed to see account.move.line
Explicitely refresh invoice browse_record(...) in order to have correct 'date' in account.move.
Use context_today() date instead of time.strftime() for date_invoice. (opw 611210)
As the different sales teams might have different sales workflows, this will allow the user to define the shipping policy based on the sales team.
This will be particularly useful to differentiate the workflows of e-commerce sales and usual sales.
- fixed call to a wrong method
- fixed button display, now based on the standard way of managing karma (popup when
not having the required karma)
- fixed button display karma computation
- some css tweaking for this button
At the confirmation of a bank statement, the name may not be set (e.g. generated by point of sale). This field is not requred so make a fallack on the statement line (which is required).
A new ir.sequence is generated at pos.config creation for the orders. However it was not used as the type was not set. The fallback was done on the general sequence.
In addition to the sequences being shared, it was not possible to create a pos.order in multicompany (no sequence found for user company, name was null).
Same issue for the pos.order.line.
This patch generates correctly pos.order and pos.order.line sequences at pos.config creation.
Instead of using the pos.config sequence to generate session number (not what this field was intended to), use the existing sequence for pos.session.
Remove company_id value on default pos.session sequence to make sure it's shared between companies and correctly set the prefix.
If the pos.config is not properly configured for multicompany (e.g. using location belonging to another company), launching a session with this config may fail (access rights).
This prevents to configure an incorrect point of sale in the first place.
Jérome Maes