Hello Flexmonster-Team,
Previously we were able to apply a filter via the UI on data, set the "filters"-parameter of the FieldMappingObject for this field to "false" and have the filter still show up but prevent the option to change those filters as other members were not loaded.
We set the filters-parameter by directly adding the according json-blocks to our configuration file.
We've only every used this method with one customer and on only one pivot so we can't say exactly when this behaviour changed. Now, when we set the filters-parameter to false, we neither see the field in the filters list, nor is the filter active.
According to our programmers the request sent by Flexmonster (btw. we are using a custom data source and Flexmonster v. 2.9.89) does not contain the field where the filters parameter was set to false.
Can you confirm this on your side as well?
Please let me know wether I can provide any further information.
Kind regards,
Florian
Hello Florian,
Thank you for reaching out to us.
We would like to confirm that there was an improvement for the custom data source API in the 2.9.88 version of Flexmonster. A new filters.members
property for the custom data source API was added to the mapping. It can be used to disable the selection filter in the filter pop-up window for a particular field. When filters.members
is set to false
, the /members
request won't be sent for that field. Instead, the members will be read from the /select
response to display the data on the grid.
However, we could not reproduce the described behavior on both versions before the 2.8.88 and the latest. Could you please provide us with more details on your use case and modify the following example to show us the expected behavior: https://jsfiddle.net/flexmonster/v8y2bntf/? It would greatly help us.
Looking forward to hearing from you.
Kind regards,
Nadia