It should limit to sale or purchase that have been at least validated.
A draft or quotation (or even a canceled) order does not make a party a customer/supplier.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
...
Linked items
0
Link issues together to show that they're related.
Learn more.
I think users expect to find under those menu items (Party associated to...) all activities they also find under the respective menus (Sales/Sales and Purchase(sic)/Purchases) which means: all states of those processes.
On the contrary I would recommend to expand on the topic to also include invoices (not only sales and purchases).
Mathias Behrleadded 1 deleted label and removed 1 deleted label
I support the idea that a customer has bought something is the right definition.
There are many situations where this list can be flooded by prospects (who just fill in an e-shop for example). Nevertheless is a big change for some of us who generate few proposals.
Adding invoicing origine would make it unconsistent for sales. The party is marked "associated with a sale" but impossible to find it.
Why not adding "parties related to sale invoices" and "parties associated with purchase invoices" menu entries in the accountant profile ?
Some cases where the party is a customer but it does not have any sale:
1. Recurring contracts created with the sale_subscription module
2. Projects that will be invoiced with the project_invoice module.
Using the customer invoice will work for this cases but the invoice creation does not reflect the fact of a party becoming a customer. Indeed this fact is represented by an agreement which is reached before the invoice. For this reasons I prefer to not use the invoices but use the models that generate the invoice with a filter based on state.
Having said that, I think we should change the current aproach a little bit and use a functional field on party instead of a Wizard. This will simplify the code and ease the customization by third party modules (by only overriding the functional field domain).
On 2017-11-14 10:35, SISalp wrote:
> Why not adding "parties related to sale invoices" and "parties
> associated with purchase invoices" menu entries in the accountant
> profile ?
2017-11-14 11:05 GMT+01:00 Cédric Krier @tryton.org>:
>
> Cédric Krier <cedric.krier@b2ck.com> added the comment:
>
> On 2017-11-14 10:35, SISalp wrote:
>> Why not adding "parties related to sale invoices" and "parties
>> associated with purchase invoices" menu entries in the accountant
>> profile ?
>
> What will be the goal?
when the accountant is not in sale group, he wouldn't have parties
associated to sales, but parties associated to sale invoices instead.
just an idea, not a requirement in my mind.
Indeed I think it will be better to remove those entries.
They can be replaced by the report "Sales per Customer" and "Purchase per Supplier" which has the benefit to filter per state and also per period.
I think it is a much better solution because such listing is mainly used to follow up customers. And in this case you often want to limit to "recent" customers.
For other type of document, it is up to each module to implement such reporting if it makes sense.