Hi all,
I found two issues with the showEmptyValues flag.
1) In a json datasouce with hierarchical field you can't expand some empty nodes. Here's a JSFiddle to reproduce the issue, for example you can't expand Asia/India/2024.
2) We have a regression on the custom datasource api: we have implemented our custom data source api, which also manage the showEmptyValues (so that in the select response we add also 'empty' combination). But after upgrading to the version 2.9.54 the showEmptyValues property doesn't work anymore. Pic1.png shows the pivot with flexmonster v.2.9.53, Pic2.png shows the pivot with flexmonster v.2.9.54. Attached a solution with an hardcoded implementation of the customDataSourceApi to reproduce the issue.
Thank you in advance,
Ilaria
Hello, Ilaria!
Thank you for reaching out to us.
Please find our comments regarding the described issues below.
1) In a JSON data source with a hierarchical field, you can't expand some empty nodes.
Please note that the described behavior is expected for the showEmptyValues
field property for the hierarchical field. The 2024 year node for Asia/India is already empty, and showEmptyValues: true
shows this empty node on the grid, but we are not showing empty nodes recursively.
2) After upgrading to version 2.9.54, the showEmptyValues property doesn't work anymore.
Kindly note that showEmptyValues
feature is available only for JSON and CSV data sources. We have checked the provided project - it uses the custom data source API protocol, for which this option is not supported.
Hope you will find our answer helpful.
Feel free to contact us in case of any other questions.
Kind regards,
Solomiia
Hello Solomiia,
thank you for your reply!
1) Honestly, if I set the property showEmptyValues at 'Month' level I expect to see all month under each aggregate, regardless of the value of the parent (empty/non-empty). Moreover, in our case, we use the 'customizecell' api to allow users edit data, and the showEmptyValue propriety is needed to add values on empty month. Anyway, the fact that the 2024 is visible with the '+' button, but the '+' button doesn't work seems like a bug to the user.
2) We indeed didn't noticed the specification in the documentation, but anyway with the previous versions we were able to implement what our clients needed: a customdatasourceApi that fills empty values, and we already deployed this implemetation on our client's scenarios. Now, if this feature is no more available we can't justify such a regression. Could you please revert the changes made in version 2.9.54 that causes the switch-off of the feature?
Thanks in advance,
Best regards
Ilaria
Hello, Ilaria!
Thank you for getting back to us.
Please find our comments regarding the two discussed topics below.
1. Thank you for providing more details about your use case. We now have a better understanding of the showEmptyValues
usage in your project.
Our team agrees that for the described use case, it would be better to display the months for the empty parent as well. However, we are not sure that our current architecture will allow us to implement such behavior.
Our Dev team will research this case, and we will get back to you with the results with ETA September 18th.
2. Please note that the showEmptyValues
feature was implemented specifically for JSON and CSV data sources. For the custom data source API, the data visualization on the grid should not be impacted by the enabled showEmptyValues
property.
Our team checked the Flexmonster's behavior on our side and in your project. We can confirm that enabling showEmptyValues
property doesn't impact visualization for custom data source API, including versions before 2.9.54.
Keeping this in mind, we kindly suggest preprocessing your data before sending it to Flexmonster so it contains all necessary fields with empty values.
Hope you will find our answer helpful.
Our team will notify you about the research results.
Kind regards,
Solomiia
Hi Solomiia,
Please let me know if you need more informations.
Thank you
Ilaria
Hello, Ilaria!
Thank you for getting back to us.
Our team has finally reproduced the described behavior of the showEmptyValues
property for custom data source API. We will provide a fix so the property will be available again in 2.9.60
and further releases.
We will get back to you with both discussed updates with the ETA September 18th.
Feel free to contact us in case of any other questions.
Best regards,
Solomiia
Hello, Ilaria!
Hope you are doing well.
Our team is glad to inform you that the issue with the showEmptyValues mapping property not working properly for hierarchy levels with empty values was fixed. The issue where options.showEmptyValues stopped working for the custom data source API was fixed as well.
Both fixes are included in the 2.9.60
version of Flexmonster: https://www.flexmonster.com/release-notes/version-2-9-60/.
You are welcome to update the component: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
Please let us know if the fixes work well for you.
Looking forward to hearing your feedback.
Kind regards,
Solomiia
Hello Solomiia,
For the first issue, it is indeed solved with the new version, thank you!
For the second one: I can see now also the empty month, but now I've an issue on expanding other nodes. Take the solution I attached to the first ticket, and install version 2.9.60. You can't expand node 'Italy' for example. Please notice that the 'select' response is hardcoded, so the select response in that case would return an error, but in any case the 'select' request isn't even fired.
Thank you in advance!
Ilaria
Hello Solomiia,
I would like also to report that the in the custom datasource Api we are also facing the same issue reported as firs issue (json dataSource): if you have a month empty you can't expand the node.
Thank you!
Ilaria
Hello, Ilaria!
Thank you for your feedback.
Kindly note that now the property works the same way for JSON and custom data source API data sources. We have checked the sample project from the beginning of this thread with the 2.9.60 version of Flexmonster.
We have moved the showEmptyValues
property from the options
to the mapping
for the Date
hierarchy in the sample project:
"mapping": {
"Year": {
"type": "string",
"hierarchy": "Date",
"caption": "Year",
"showEmptyValues": true
},
"Month": {
"type": "string",
"hierarchy": "Date",
"parent": "Year",
"caption": "Month",
"showEmptyValues": true
},
//other mapping properties
}
After this change, Flexmonster shows the Cartesian product for all Date
hierarchy members, and the members of other fields are not duplicated. The result we've got is the same as on the Pic1.png provided to us at the beginning of the thread.
Please try setting showEmptyValues
for the Year
and Month
on your side, and let us know if it works well.
Looking forward to hearing from you.
Kind regards,
Solomiia
Hello, Ilaria!
Hope you are doing well.
Our team is wondering if you have some time to check out our previous message. Could you please let us know if everything works well after moving showEmptyValues
configurations to mapping?
Looking forward to hearing from you.
Kind regards,
Solomiia
Hello, Ilaria!
Hope everything is well.
Just checking in to ask if the showEmptyValues
property works well with custom data source API after moving property configurations from options
to mapping
.
Looking forward to hearing your feedback.
Kind regards,
Solomiia