I don't use billing profiles in my checkout process; I use only shipping profiles, and let billing address/etc. get handled by the payment processor.

Thus, I'd like to see the map be generated based on shipping profiles. I'll attach a patch in the comments that is commerce_customer_profile bundle-agnostic. Thoughts?

CommentFileSizeAuthor
#1 commerce_reports-1853500.patch1.02 KBjessepinho

Comments

jessepinho’s picture

StatusFileSize
new1.02 KB

Patch.

jessepinho’s picture

Hmm... on second thought, if one includes BOTH shipping and billing profiles in the checkout process, those profiles will both be counted in the query, and thus all statistics will be doubled. Perhaps we need a dropdown in a settings UI for reports to choose which profiles to look at on the map?

cvangysel’s picture

That's correct. Remember that shipping profile is a customer_profile bundle added by the commerce_shipping module, so depending on it by default would not be a good idea.

I do like the idea where the user has an option to select which customer_profile bundle it wants to use as a data source. If you supply a patch for this I'd be more than happy to work with you to get this in.

mglaman’s picture

My patch in #2125813: Visualization to Charts Module Migration decouples Commerce Reports from Visualization to Charts and replaces the map with a view. This view provides display based on billing or shipping profiles and is not hardcoded.

If you could test and review that patch it may solve your problems.

mglaman’s picture

Issue summary: View changes
Status: Active » Needs review
dpearcefl’s picture

Does this issue still exist against the latest dev release?

mglaman’s picture

Please review the 7.x-4.x release which adds this feature, and note module changes as stated in #2129735: Commerce Reports 4.x Review

mglaman’s picture

Status: Needs review » Fixed

In 4.x customer map has been moved to view and supports billing & shipping profiles. However, currently experiencing bug #2161563: Customer Profile Map does not render on Reports dashboard

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.