Despite the COVID-19 outbreak, our team continues operating at full speed. We are always here to support and answer all your questions.

Feel free to reach out by filling this quick form.

Fill the form
Get Free Trial

bug: Custom api – the fourth report filter is not sent in the select request

Re-Open
Cedric Kalume asked on September 10, 2020

Version: 2.8.15
Hello,
when using the custom api i have noticed a bug, the fourth(4) report filter is never sent to the server during the select request. All the others do.
Tested with 1,2, 3, 4, 5, 6 and 7 reports filters, in multiple orders, only the  fourth one is missing.
What can I do to resolve this issue?

Attachments:
select.json
filters.png

12 answers

Public
Illia Yatsyshyn Illia Yatsyshyn Flexmonster September 10, 2020

Hello, Cedric,
 
Thank you for reporting the problem.
 
The fix is going to be provided with a minor update ETA Oct 05.
Our team will notify you as soon as the version with a fix is available to download.
 
We hope it works for you.
Please let us know in case any additional questions arise.
 
Best regards,
Illia

Public
Illia Yatsyshyn Illia Yatsyshyn Flexmonster October 6, 2020

Hello, Cedric,
 
We are happy to let you know that the issue with report filters ignored when using the custom API data source was fixed.
This is available in the 2.8.17 version of Flexmonster.
 
You are welcome to update the component.
Here is our updating to the latest version guide for assistance.
 
Please let us know if everything works.
 
Regards,
Illia

Public
Illia Yatsyshyn Illia Yatsyshyn Flexmonster October 13, 2020

Hello, Cedric,
 
We want to take an interest in whether the recent fix managed to resolve the problem with report filters.
 
Our team is looking forward to hearing your feedback.
 
Best regards,
Illia

Public
Cedric Kalume October 15, 2020

Hi using version October 2020 (v. 2.8.17) is indeed working,
but there is a new problem, when loading a slice then using options->flat form, the flat table select request does not add the report filters fields to the fields list which result in empty cells and an error when trying to export the data to excel.

Public
Cedric Kalume October 15, 2020

This can be replicated by putting one field in report filter, one in Columns, one in Rows and one in Values and then clicking options -> flat form

Public
Illia Yatsyshyn Illia Yatsyshyn Flexmonster October 16, 2020

Hello, Cedric,
 
Thank you for your feedback and for reporting the problem.
 
We have managed to reproduce the described behavior on our side.
The fix is going to be provided with a minor update ETA Nov 16.
Our team will notify you as soon as the version with a fix is available to download.
 
Feel free to reach out in case any other questions arise.
 
Best regards,
Illia

Public
Illia Yatsyshyn Illia Yatsyshyn Flexmonster November 17, 2020

Hello, Cedric,
 
We are happy to let you know that the issue with using reportFilters in the flat form was fixed.
 
This is provided in the 2.8.20 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 everything works.
 
Best Regards,
Illia

Public
Illia Yatsyshyn Illia Yatsyshyn Flexmonster November 24, 2020

Hello, Cedric,
 
We want to take an interest in whether you had some time to test the recent fix.
Please let us know if it works well for you.
 
Our team is looking forward to your feedback.
 
Best regards,
Illia

Public
Cedric Kalume November 24, 2020

Hello,
All seems well for now

Public
Cedric Kalume November 25, 2020

Hello,
 
The recent fix does resolve the error however I do have a complaint:
when an invalid data is provided with the custom API, the error message is unreadable.
Is is possible to show the column name as well as the value which caused the error in error modal?
 
thanks,
Cedric Kalume

Public
Milena Pechura Milena Pechura Flexmonster 7 days ago

Hello, Cedric,
 
We are glad to hear that the issue is resolved.
 
Regarding your question:
Our team would like to explain that our component does not show the dev errors to the end-users because the client side is supposed to display only the issues that the client can resolve.
With this in mind, we kindly suggest implementing the desirable error handling behavior on the server side.
 
Please let us know if any other questions arise.
 
Best regards,
Milena

Public
Cedric Kalume 2 days ago

Hello Milena,
 
I do indeed understand however the error popup message is unintelligible for our client because it gives either the error value or the result of a failed function call due to wrong datatype.
 
So I would like to suggest replacing the error value with the unique name of the field which would allow everyone to quickly find out where the very occasional error occurred. 
However that is simply a suggestion.
 
Regards

Please login or Register to Submit Answer