Customer Tree-View shows confusing address-information

[René Glauser]

In the tree-view of the customer-menu there is always shown the address-information of the customers first address in alphabet (A before B) event if it is a "contact" and not the customers default-address. Tree-View should always show the information for "Default"-Address of customer.

[Amit Parik (amit-parik)]

Hello,

I have checked your issue at my end. But all are working as expected.

So would you please provide the proper example or screen-shots on this where you faced the problem.

Thanks

[René Glauser (rene-glauser)]

Hello,
In the attached screenshots you can see my problem:
1) Customer-treeview that shows address-information of contact
2) Address of Type "Contact"
3) Address of Type "Default"

Problem: In my opinion tree-view should not show address-information of "contact" but address-Information of "Default"-Address......or what is the logic behind the adress-information displayd in tree-view?

[Amit Parik (amit-parik)]

Hello,

This is not a generalize issue and we need to more discussion on this.
So for now I am set it to opinion .

New suggestion are welcomed!

Thanks for the understanding!

[René Glauser (rene-glauser)]

Hello
In my opinion it makes no sense and is very confusing, when customer tree-view shows something else than the main company address-information. When I open customer tree-view I am not interested in information about contacts of a customer but mainly about the street and city where customer is located.
Can this be customized if I always want to see information about default-address of customer in tree-view?

[Gabriel Lopez (icpgp)]

Hi, I'm interested in a solution for this too, found any?

[René Glauser (rene-glauser)]

no...
in my case, when I print a report, the same contact-information of my company that is shown in the customer-tree-view is also shown as contact-information of my company on top of the standard report, what makes absolutely no sense....
in my opinion its a bug and not a opinion..

[Robin (www.cgbs.com.au) (robin-cgbs)]

Whilst I see it as not a bug, it certainly appears to be a design flaw.

I too make the assumption that the address details on the partner tree are the default values, and not those of some contact related to the partner. I know that is the way we work, and our clients wish to work as well.

The issue is because of the _order of the res.partner.address and the fact that the fields are related fields.

Changing them to function fields and loading the fields with values from the default address if it exists is one solution. One could even do this with another module (inheriting from res.partner and changing fields like city from a related field to one that is a function field).

[René Glauser (rene-glauser)]

Until now I use the following workaround: I changed the sort-order in "res.partner.py" for res_partner_address from _order = 'type, name' to _order = 'id, type, name'
This means that in a tree-view, where address-information is shown of a partner, always the address with the lowest id will be shown first, when at the time of creation of the partner, the defaul-address is created before any contact of that partner.
The problem of the standard sort-order _order = 'type, name' is, that there will never be displayed the defaul-address of a partner in a tree-view if there is one contact saved for that partner....