Cancel a long running report

Answered
Bill Hamill asked on May 29, 2019

Is there a way to cancel a long running report? I’m using MSAS. I’ve seen both https://www.flexmonster.com/question/how-to-cancel-report-loading/ and https://www.flexmonster.com/question/cancel-loading-report/ and tried both clear() and setReport({}). Neither seems to work. Both seem to interrupt the query momentarily, but the query just picks up where it left off.

4 answers

Public
Vera Didenko Flexmonster May 31, 2019

Hello, Bill,
 
Thank you for reaching out to us.
 
We have not managed to reproduce the issue at our end: flexmonster.clear() works fine.
 
Please provide more details, for example, a sample, sample report, where the problem occurs so we may be able to help you solve the problem.
We also kindly advise testing your problem on our demo and in case the issue occurs, please provide steps on how the issue can be reproduced.
 
We are looking forward to hearing from you.
 
Best Regards,
Vera

Public
Bill Hamill May 31, 2019

Hi Vera,
It will be difficult to provide a sample report as I can’t share the OLAP cube.
I can’t seem to reproduce the problem with your demo, but that dataset is kinda small and doesn’t go through the accelerator.
Additional details… After I call clear() from my application, the “Loading members…” popup continues to update. Also, we’re accessing the cube via the Flexmonster accelerator it continues to log messages like:
2019-05-31 13:12:06.4293 | TRACE | Loading members…[Builder].[Builder Name] – 11
2019-05-31 13:12:06.4293 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:07.2417 | TRACE | Loading members…[Builder].[Builder Name] – 12
2019-05-31 13:12:07.2417 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:08.0699 | TRACE | Loading members…[Builder].[Builder Name] – 13
2019-05-31 13:12:08.0699 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:09.0074 | TRACE | Loading members…[Builder].[Builder Name] – 14
2019-05-31 13:12:09.0230 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:10.0386 | TRACE | Loading members…[Builder].[Builder Name] – 15
2019-05-31 13:12:10.0386 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:10.9136 | TRACE | Loading members…[Builder].[Builder Name] – 16
2019-05-31 13:12:10.9136 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:11.9919 | TRACE | Loading members…[Builder].[Builder Name] – 17
2019-05-31 13:12:11.9919 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:13.0700 | TRACE | Loading members…[Builder].[Builder Name] – 18
2019-05-31 13:12:13.0700 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:14.4136 | TRACE | Loading members…[Builder].[Builder Name] – 19
2019-05-31 13:12:14.4136 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:15.9918 | TRACE | Loading members…[Builder].[Builder Name] – 20
2019-05-31 13:12:15.9918 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:17.2262 | TRACE | Loading members…[Builder].[Builder Name] – 21
2019-05-31 13:12:17.2418 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:18.4293 | TRACE | Loading members…[Builder].[Builder Name] – 22
2019-05-31 13:12:18.4293 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:19.5856 | TRACE | Loading members…[Builder].[Builder Name] – 23
2019-05-31 13:12:19.6011 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:20.7574 | TRACE | Loading members…[Builder].[Builder Name] – 24
2019-05-31 13:12:20.7574 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:21.9137 | TRACE | Loading members…[Builder].[Builder Name] – 25
2019-05-31 13:12:21.9137 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:23.1324 | TRACE | Loading members…[Builder].[Builder Name] – 26
2019-05-31 13:12:23.1324 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:24.4449 | TRACE | Loading members…[Builder].[Builder Name] – 27
2019-05-31 13:12:24.4606 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:25.7262 | TRACE | Loading members…[Builder].[Builder Name] – 28
2019-05-31 13:12:25.7262 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
2019-05-31 13:12:27.0387 | TRACE | Loading members…[Builder].[Builder Name] – 29
2019-05-31 13:12:27.0387 | TRACE | CACHE: Get – Flexmonster.Accelerator.Models.DiscoverMembersArgs
Also, I’ve tried with and without CACHE_ENABLED and while the log messages change a little, the effect is the same.
Thanks for your help.

Public
Vera Didenko Flexmonster June 3, 2019

Hello, Bill,
 
Thank you for your reply.
 
It is important to point out that our demo on the website is using Flexmonster Accelerator.
 
We have managed to reproduce an issue connected with using flexmonster.clear() or flexmonster.setReport({}) to interrupt the data loading process.
 
Steps how to reproduce the issue on our website:

1) Go to our Demo: http://www.flexmonster.com/demos/connect-msas/
2) Set network to fast 3G
3) Choose a lot of fields in the Field List (For Rows, Columns, Values)
4) In the browser console prepare flexmonster.clear(); or flexmonster.setReport({}); command
5) Click Apply in the Field List 
6) When the loading message shows the percentage of the loading data progress, enter the flexmonster.clear(); or flexmonster.setReport({}); command.
7) An error will appear in the console (sometimes if using flexmonster.clear() the loading window will appear once more after the error is thrown)
 
Although we cannot be completely sure that the problem we have found is the one you are encountering, our team will provide a fix for it and we hope it will resolve the issue for your case as well.
 
The fix will be available in the minor release of Flexmonster with the ETA 1st of July.
 
We would like to mention that it would help our team a lot if you could send us a sample (with sample data) or give us access to your environment where the issue is reproducible for testing purposes. This can be done via email.
 
Feel free to contact us in case any questions arise.
 
Best Regards,
Vera

Public
Bill Hamill June 4, 2019

Thanks for looking into this. I still don’t think I can send a sample since our sample data is proprietary. I will certainly test the fix in July to see if it also fixes my problem. I will update this thread with what I find.

Please login or Register to Submit Answer