can still be used.

view. If the associated analytic structures were defined with a model name,
which did not match the original model technical name, the system was unable to
determine, if the analytic codes were wanted as required.

analytic codes, when an analytic dimension is bound to a model.

as required.
The 'fields_get' method was called with invalid arguments. The consequence was
that this method was no more able to list analytic fields. This resulted in
conflicts between the results of 'field_get' and 'fields_view_get'. It was
no more possible to decide to update all Odoo modules.

Updated the translations.

Behind-the-scenes objects; main object security rules are enough.

Will be done better (more cases handled, more comments) by grafting rev
d11003bb260b.

When binding a dimension to a model, if there is a 'False' value instead of a
parent code, when seeking one, no ID must be extracted.

The override of the 'create' method must return an ID, when binding a dimension
to a model.

Updated the change log.

created analytic code name, is not immediately filled in the first write
processes, and only filled afterwards.

the 'extract_values' method.
This method was used to propagate the analytic codes of a specific object to
another one on the common dimensions.

instruction was missing.

(There are cases where the dictionary var is actually None...)