I got the following error

EntityMetadataWrapperException: Unable to get the data property commerce_total as the parent data structure is not set. in EntityStructureWrapper->getPropertyValue() line 442 ...

...on a data export of a view (at a commerce site) with some complex 'relationships' between line items and orders.

I sorted it out by using 'filtering criteria' to filter out rows that had empty results.
Said in another way: The fields generated from the relations was sometimes empty and that gave me errors...

Not sure if this is a views data export, a views, a commerce or an entity related error - or even a "real" error - but I got it after using views_data_export!
My main reason for posting it here is that it might help somebody else with a similar error :)

Comments

haradhansharma’s picture

haradhansharma commented

During Checkout process, when clicking on My shipping information is the same as my billing information. below notice are getting, ---- but when entering separate address, then this massage are not showing!!

EntityMetadataWrapperException: Unable to get the data property commerce_total as the parent data structure is not set. in EntityStructureWrapper->getPropertyValue() (line 442

need solution!

steven jones’s picture

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

What data exports have you set up?

steven jones’s picture

steven jones commented
Issue summary: View changes

corrected last line for better understandability :)

steven jones’s picture

steven jones commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » 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 :)