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.
⋅ 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
⋅ 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.
⋅ 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/js/connect-ssas/
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
⋅ 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.
⋅ July 2, 2019
Hello, Bill,
We are happy to let you know that the API call clear was fixed for XMLA data sources.
This is included in the 2.7.9 version of Flexmonster: https://www.flexmonster.com/release-notes/
You are welcome to update the component.
Here is our updating to the latest version guide for assistance: https://www.flexmonster.com/doc/updating-to-the-latest-version/
Please let us know if this helps to resolve the issue for your case.
We are looking forward to hearing from you.
Best Regards,
Vera
⋅ July 9, 2019
Status update... I'm having trouble downloading the package (for MSAS). Windows Defender is detecting a virus. I don't know if this is a problem on my end (maybe someone else has seen this?). I don't have much control over that intended server. I'm still working on it.
⋅ July 10, 2019
Hello, Bill,
Thank you for writing.
We were previously reported, that some antivirus engines are showing the false positive identification of the Flexmonster Accelerator service as a threat.
For this particular case, we provided a fix for clear() API call for Flexmonster Pivot (only the client-side) so we suggest updating only the client this time. This can be done by downloading another package (e.g., Pivot Table for JSON data sources) and get the updated flexmonster/ folder from here.
Please let us know if you manage to update successfully.
Regards,
Tanya
⋅ July 22, 2019
Hi Tanya,
I was able to get the new version (2.7.10) running following your suggestion (to leave the old Accelerator in place). Unfortunately, I still can't cancel the request as I expect to...
From my posted log output above, you see that I go through 29 iteration of "Loading members...". If I issue a clear() during any one of these iterations, it just continues to the next one. I see the progress alerts showing 3%, 6%, 9%... I can issue the clear() more than 20 times during the "Load members..." phase. Note that when I issue the clear() during the "Loading data..." phase, the request is finally canceled.
I tried to increase the scale your demo (https://www.flexmonster.com/demos/js/connect-ssas/) by changing rows to "Sales Order Number". This produces many more rows and produces 3 "Loading members..." iterations. I find that I see behavior similar to my problem. If I issue the clear() during the first (36%) iteration, the demo simply continues to the second (72%) iteration. I haven't been able to create a demo report with more than 3 iterations. I've attached a saved report to help duplicate the problem.
Thanks for your help.
⋅ July 23, 2019
Hello, Bill,
Thank you for your response and for describing the problem in detail.
This helped us a lot to understand the situation better.
Our team will provide a fix for this issue in the minor release version with the ETA 12th of August.
You are welcome to contact us in case of questions.
Best Regards,
Vera
⋅ July 23, 2019
Great! Thanks. I will test the fix when it comes out and let you know how it goes.
⋅ August 14, 2019
Hello, Bill,
We are happy to let you know that the issue with clear() method for SSAS was fixed.
This is included in the 2.7.12 version of Flexmonster: https://www.flexmonster.com/release-notes/
You are welcome to update the component.
Here is our updating to the latest version guide for assistance: https://www.flexmonster.com/doc/updating-to-the-latest-version/
We would like to point out that Flexmonster Accelerator needs to be updated as well: https://www.flexmonster.com/doc/updating-to-the-latest-version/#!accelerator
Please let us know if everything works.
Best Regards,
Vera
⋅ August 19, 2019
Hi Vera,
Thanks for continuing to look into this...
I tried the fix in version 2.7.12. I updated both the client and the accelerator. I do see that if I wait through the "Loading members..." phase and call flexmonster.clear() during the "Loading data..." phase, it does seem to cancel the query.
But if I call flexmonster.clear() during the "Loading members..." phase, I see the same thing as before: the "Loading members..." message disappears for a moment, then reappears with the next percentage, e.g., "Builder Name - 21% (60000 of 290464)". As in the example above, we can go through 29 iterations of the "Loading members..." message before we get to "Loading data...".
Can you duplicate that? Is there any way to cancel the query during the "Loading members..." phase?
⋅ August 20, 2019
Hello Bill,
Thank you for your feedback.
We have taken a bigger data set and limited the network speed.
With such pre-conditions, the issue seems to be still reproducible. We will continue looking into it.
The fix is going to be released in the version with ETA Sep 9.
We will notify you of the results.
Regards,
Dmytro
⋅ September 12, 2019
Hello, Bill,
We are happy to let you know that the issue with canceling data loading for OLAP cube was fixed.
This is available in the 2.7.14 version of Flexmonster: https://www.flexmonster.com/release-notes/
You are welcome to update the component: https://www.flexmonster.com/doc/updating-to-the-latest-version/
A kind reminder is to update Flexmonster Accelerator also: https://www.flexmonster.com/doc/updating-to-the-latest-version/#!accelerator
Please let us know if everything works fine for you.
Best Regards,
Vera
