I created a custom version of the Orders list View. I added an Order Balance field column.

This view is no longer accessible. I get a Server Error page when i try to view the page. And when I view the admin page for the View, it initially produces a javascript popup that says:

An AJAX HTTP error occurred.
HTTP Result Code: 500
Debugging information follows.
Path: /admin/structure/views/view/commerce_orders_filtered/preview/admin_page/ajax
StatusText: Internal Server Error
ResponseText: EntityMetadataWrapperException: Unknown data property commerce_order_total. in EntityStructureWrapper->getPropertyInfo() (line 339 of /path-to-drupal-folder/sites/all/modules/entity/includes/entity.wrapper.inc).

Perhaps needless to say, In the View admin, the preview does not display. Does this field need a relationship for it to not crash the View? I tried to add the Line Item relationship and that didn't help. What's wrong here?

Comments

rszrama’s picture

rszrama commented
Category: bug » support
Status: Active » Postponed (maintainer needs more info)

I don't have any problem adding the "Order Balance" field to the default Orders View using Commerce Kickstart with Views 3.3. Is there some other customization on this View? The only reason you should see the error you're seeing I'd suppose is if you're missing the order total price field (which I doubt, as that would be causing plenty of other problems you'd have encountered before now).

Please post the View you're using that no longer works along with more information about your module versions and configuration, and we can reclassify this as a bug if need be.

rszrama’s picture

rszrama commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Oh! You know, this could play into your other issue. Perhaps the problem isn't that the payment balance function can't find the payment transactions but that it can't find the order total it should be subtracting from. : ?

In any event, I can't reproduce this, so if there was a legitimate bug in here, I'll assume it's been fixed in 1.3 or 1.4.