Handling issues when MDX queries are invalid

Question

There are many reasons an MDX query generated by the OLAP Engine may be invalid. If the query is created by the slice-and-dice user interface errors are less likely but if the cube behind has changed saved reports may no longer be valid.

More common for me is to be creating reports manually and making a mistake. Here's a StackBlitz link to an example.

As you will see in the example, the error is never reported. The user only knows there is a problem because the spinner does not stop.

Of course, I can fix my problem. But is there a better way to handle these conditions? If there's an error with the MDX, Analysis Services will report the error in its response. Is there a mechanism to grab the error message?

Thanks.

Rajeshkannah G · Answer

Hi Bill,We regret to inform you that we currently do not have an
option to capture the error message when MDX queries are invalid. Please let us know if you have any concerns.Regards,Rajeshkannah Gopalakrishnan

Bill Seddon · Answer

OK. But is there some what to handle the error? When Analysis Services responds with an error, the ./olap/olapEngine implementation handles it but suppresses which means even Syncfusion's PivotView code is unable to update its user interface or let the user know.

Surely something better can be done?

AngelinFaithSheeba PaulvannanRajadurai · Answer

Hi Bill,Currently, we have “actionFailure” event in Pivot Table that will be triggered to
display an error message when we do UI actions in the pivot table that are not
successfully completed at runtime. However, currently we are facing an issue
that actionfailure event not thrown error during initial rendering. We
believe that this failure event will fulfil your need. Thus, we have logged this
as a bug " Exception not throw when OLAP cube data fetch with
improper MDX query during initial rendering". And the fix for this
issue will be included in our August last weekly release which is scheduled to
be rolled out on August 30, 2023. You can track the status with the feedback
link below.Feedback: https://www.syncfusion.com/feedback/46150/exception-not-throw-when-olap-cube-data-fetch-with-improper-mdx-query-duringRegards,Angelin Faith Sheeba.

Bill Seddon · Answer

Thanks for the update.  You guys provide great support.  It's great to know it will be possible to respond to an error condition.

AngelinFaithSheeba PaulvannanRajadurai · Answer

Hi Bill,Sorry for the inconvenience. We are now unable to extract
error information at the client-side from the OLAP cube because we acquire the
cell information from the OLAP as XMLA (SOAP-based XML). To obtain error
information from the service, we must first confirm the possibilities with our
current SOAP structure. As a result, we considered your request as an
improvement. Because we are already working on high priority items for our
upcoming 2023 Vol 3 release, this requirement will be available in
our 2023 Vol 4 release, which is estimated to be rolled out at the
end of December 2023.We appreciate your patience until then.Regards,Angelin Faith Sheeba.

Bill Seddon · Answer

Thanks for the update.

AngelinFaithSheeba PaulvannanRajadurai · Answer

Hi Bill,We apologize
for not being able to include this feature request in our Vol 4 main release as
promised due to other high priority items already in the queue for
consideration. However, considering your importance as priority, we will
include this feature in our upcoming 2024 Volume 4 SP release which is estimated
to be rolled out at end of January, 2024. You can track the status of this
using the below feedback.Feedback: https://www.syncfusion.com/feedback/46150/exception-not-throw-when-olap-cube-data-fetch-with-improper-mdx-query-duringWe appreciate your patience until
then.Regards,Angelin
Faith Sheeba

AngelinFaithSheeba PaulvannanRajadurai · Answer

Hi Bill,Thank you for the patience. We are
glad to announce that our Essential Studio 2023 Volume 4 SP Release V24.2.3 is
rolled out and the
improvement “Exception not throw when OLAP
cube data fetch with improper MDX query during initial rendering” has been included in this release.
And now you can able to view the error information using the actionFailure event.
Please refer the below code example.Code Example:

actionFailure: function(args){
        // You can capture the
  error information here.
          console.log(args.errorInfo);
      },

Output screenshot:Meanwhile, we have prepared a sample
for your reference.Sample: https://stackblitz.com/edit/ar7ws8-2zq7dx?file=index.html,index.jsWe thank you for your
support and appreciate your patience in waiting for this release. Please get in
touch with us if you would require any further assistance.Regards,Angelin Faith Sheeba.

Bill Seddon · Answer

Perfect.  Thanks.  That work and we are now able to respond to errors from AS.

AngelinFaithSheeba PaulvannanRajadurai · Answer

Hi Bill,Thanks for the update. Please
contact us if you have any other queries. We are always happy to
assist you.Regards,Angelin Faith Sheeba.

Bill Seddon · Answer

Hi, having worked with the fix, I've come across an introduced problem. Let me know if this should be a new ticket.The issue is within the function doAjaxPost of ./src/base/olap/engine.js. This function contains the line: if (!body.querySelector('DiscoverResponse').querySelector('return').querySelector('row')) { ... }In most cases, checking the element has at least one element is a good idea. However, it is possible for a CUBE to have no named sets. To check for named sets the OLAPEngine generates the request:

MDSCHEMA_SETS Quarterly Outcomes_flow_combined Quarterly 1033 When the query is sent to one of our cubes which has no named sets, the response below is received. It's valid and correct but because it does not include elements the condition in the 'doAjaxPost' function creates an error. My solution is to set _this.errorList = null;in the function 'loadNamedSetElements'.

AngelinFaithSheeba PaulvannanRajadurai · Answer

Hi Bill,We have created a separate forum to track the “Pivot
table throws an error and breaks while connecting an OLAP cube with no named
set” issue. Please follow the below forum for further follow up.Forum:
https://forumassist.syncfusion.com/186589Please let us know if you have any concerns.Regards,Angelin Faith Sheeba.