I've created a data export to create a CSV file that contains Ubercart customer order data. When I add fields to be exported, the zone (province/state) and country fields aren't listed with with other fields that can be selected for export. How can they be added?

CommentFileSizeAuthor
#2 Screen Shot 2013-01-08 at 10.22.00 AM.png62.4 KBavalot

Comments

AaronNiemi’s picture

AaronNiemi commented
Version: 7.x-3.0-beta6 » 7.x-3.x-dev

I'm wondering the same thing.

There is no reference to zone or zone id from views.

TIA
-Aaron

avalot’s picture

avalot commented
Priority: Normal » Major
StatusFileSize
new Screen Shot of available billing fields in views of Ubercart.png62.4 KB

I have the same issue. When building a view of Ordered_Products, and adding fields, I can see most of the Billing Address and Shipping Address fields, but not Country or "Zone" (aka State/Province.)

This is a major impediment to doing business. Any ideas what could be causing this?

steven jones’s picture

steven jones commented
Status: Active » Postponed (maintainer needs more info)

Sorry, are you saying that you can't add the fields in the Views UI, or that you can't export the data once you've added the fields?

hazah’s picture

hazah commented
Issue summary: View changes

Fairly certain that the screenshots illustrate what the problem is. One cannot add the FIELDS to any view that needs columns of STATE or COUNTRY.

Let me know if I can clarify this any further.

hazah’s picture

hazah commented
Status: Postponed (maintainer needs more info) » Active
steven jones’s picture

steven jones commented
Status: Active » Closed (won't fix)

Sorry for the lack of attention to your issue, please accept my apologies.

Drupal 7 is going to be end-of-life'd by the community in approximately 1 month.

As such, I am closing all non-critical looking, non-PHP compatibility issues for Views Data Export to tidy up the issue queues and reduce the noise. You can read about this on #3492246: Close down Drupal 7 issues.

If you feel like this issue has been closed by mistake, please do comment about re-opening it.
If you feel like the ticket is still relevant for the 8.x-1.x version of the module, then please search for a duplicate issue first, and if there really isn't one (and you've looked properly) then change the version on the ticket and re-open.

Thanks to everyone involved in this issue: for reporting it, and moving it along, it is truly appreciated.
The Drupal community wouldn't be what it is today without your involvement and effort, so I'm sorry that we couldn't get this issue resolved. Hopefully we'll work together in a future issue though, and get that one resolved :)