Contributors mailing list archives


Re: PROPOSAL :: AccountMove v9 - hidden tag

- 03/10/2015 03:17:37
In order to rely on journals programmatically, we would need to make them immutable for the user. But journals are inherently a user space concept. That said, journals are quite the same basic idea. Ideal however would be a hidden related model, which developers can use for custom views, amplified and adaptive account move model and to be relied upon for reporting aggregation.

A journal's usage could then be restricted to document types (configured on the journal), to help avoid inconsistencies.
>That's not what the combination of journal + automated actions + sequence engine does?

Nope, I'm talking of the label field (technical name: account.move name). The deeper sense of this proposal is to provide a standard way of making sure, that the Label (or name field) - which is otherwise a freeby wIt is meant to assuer that the label of a certain document type

El vie., 2 oct. 2015 a las 19:07, Nhomar Hernandez (<>) escribió:

On Fri, Oct 2, 2015 at 6:53 PM, David Arnold <> wrote:

One example would be a treasury bill, so I would create Treasury Bill Tag and create a custom module that helps to encode a very specific label for those journal items (GTDEM2Y:GOV - Bloomberg Code). Then, having entry type encoded in the tag, It is very easy to create specialized reporting for those type of documents across the software.

The value of an official way to do this, is increased ecosystem consistency and higher developer effectiveness, among others.

What do you think?

That's not what the combination of journal + automated actions + sequence engine does?

Nhomar Hernandez
CEO Vauxoo.
Twitter: @nhomar
Odoo Gold Partner
Móvil Venezuela:
+58 4144110269
Móvil México:
+52 1 4773933942

Post to: