I am having the same issue.  I found ID:54188 in the Sage Knowledgebase but I don't have a view in the failing view.  The view was working before the upgrade from MAS 500 ERP 7.40.3.0 to Sage 500 ERP 2013 October 2013 version 7.50.4.0.  The view runs in SQL Manager and the data looks good.

It would be good to have more information from sage on the cause.

Rich Garrett

DSG, Inc.

I am taking my view and column by column remarking out to figure out which ones are 'unliked' or is that 'not liked'.    This is very frustrating.  We are having some other issues with BIE which I am still working through.  Tougher upgrade than we were expecting.  We tested all of our main functionality well but missed a lot of small stuff (like customizer doesn't work well in Customer Maintenance!).

Thx. for your post Rich.

Do you have Grouping & Summarization enabled within the BIE view? It sounds as if there may be a problem with the summaraization inside the Explore task rather than the underlying SQL view itself.

No grouping/summarization.  The view won't even run!

To be clear the view in SQL runs fine but in 500 no run.

It's a custom view, one of over 100 we have on our system.  The upgrade broke a fair amount of BIE stuff.  I've had to delete specific views because they errored and were the users default view.  Ugh!

John

Is this a custom view or a native Sage view?

It's a custom view.  Though we also had problems with standard views.

I found my issue.  I had created a view for a table that a third party developer created for Sage 500.  The table contained a field weight.  Weight is not a reserved word in SQL but it is part of the MS SQL syntax.  I tried a number of different adjustment and have found a work around.

I cleared Weight from the Permanent Column on the Column Mapping Tab.  Then typed Weight in the Override Caption.  Now it works.

Rich Garrett

DSG, Inc.

Rich - That is definitely the answer in some cases.  We found quite a few problems besides that though with views and how they are defined in Maintain Business Insights Views.  However we were able to fix them by either rebuilding the view or changing it in Maintain BI Views.  I'm pretty surprised this hasn't come up before.  This would make a good blog post (hint hint Sage).  Also note that some of the standard views in Maintain BI Views won't save unless you fix the problems in the meta data (Customers is one example).