Duplicate select request while rows collapse

Answered
carrie asked on March 1, 2022

hello, is there a way to stop duplicate select requests while rows are collapsing?
The server side needs a long time to calculate pivot data sources, so we expect to send just one select request when the pivot table is initial, is it possible to achieve this demand?
 
Many thanks
carrie

6 answers

Public
Nadia Khodakivska Nadia Khodakivska Flexmonster March 1, 2022

Hello, Carrie,
 
Thank you for reaching out to us.
 
Please note that in Flexmonster, collapsing a row doesn't require any select requests.
If we understood you correctly, you want to expand data by sending a select request only once. Then when collapsing and expanding it once again, you expect the data to be already received without further requests to the server. Could you please confirm if it is what you wish to achieve? It will help us to find you a suitable solution for your case.
 
Looking forward to hearing from you.
 
Kind regards,
Nadia

Public
carrie March 2, 2022

Thanks for your reply Nadia.
I’m sorry. Maybe my previous description is inaccurate. Please see the attachments, three requests are sent when the initial pivot table row is in the grouped state, but when the row is not in the grouped state, only one select request is sent.
What I need to do now:
1 Sending a select request only once when the initial pivot table row is in the grouped state;
2 Without further requests to the server when collapsing and expanding the row;

Looking forward to your reply.
Carrie

Public
Nadia Khodakivska Nadia Khodakivska Flexmonster March 3, 2022

Hello, Carrie,
 
Thank you for providing detailed information and screenshots.
 
Please find our comments below:
 

  1. Kindly note that the current architecture of Flexmonster requires sending several requests to get the data. However, our team will research possible solutions regarding optimizing the number of requests and provide you with results ETA March 21. 
  2. One of the main ideas of custom data source API is passing only the data required for the current report instead of loading the whole data set. It allows increasing the speed and handling much more extensive data volumes due to the fact that the client’s machine does not have to store the whole data set. Therefore, each new expand requires sending a new request. 
    For your case, we recommend caching specific responses. For example, prepare responses to the requests you frequently receive to speed up the process.

 
You are welcome to write to us in case further questions arise.
 
Kind regards,
Nadia

Public
Nadia Khodakivska Nadia Khodakivska Flexmonster March 22, 2022

Hello, Carrie,
 
We are pleased to inform you that the issue with duplicate requests was fixed.
 
This fix is available in the 2.9.21 version of Flexmonster: https://www.flexmonster.com/release-notes/version-2-9-21/ 
 
You are welcome to update the component: https://www.flexmonster.com/doc/updating-to-the-latest-version/  
 
Please let us know if it works for you. Feel free to contact us if other questions arise.
 
Kind regards,
Nadia

Public
carrie April 15, 2022

Hi Nadia,
I have upgraded flexmonster version to 2.9.22, I compared the number of select requests before and after the updated version. In this case, three select requests were sent before, but now they are sent twice, I don't know why the two requests are of different types, but the number of requests has indeed decreased.
 
Best regards,
Carrie

Public
Nadia Khodakivska Nadia Khodakivska Flexmonster April 15, 2022

Hi, Carrie,
 
Thank you for the feedback.
 
We would like to explain that currently, the architecture of Flexmonster requires sending several select requests to get the data - the first request is for the external level and the other ones for internal levels. So the two requests from your screenshots are expected. This behavior ensures the correct presentation of the data.
 
We hope it helps. You are welcome to write to us in case further questions arise.
 
Kind regards,
Nadia 

Please login or Register to Submit Answer