asked on May 17, 2023
Hi Team,
I'm trying to get a hierarchy configured in FDS and have a couple of issues.
When displaying the data in a form, the date (day) column shows without formatting to the correct date format. Only certain dates are formatted correctly. All data is in the correct format of 'YYYY-MM-DD'. This display issue does not occur for all records.
This is causing the sort order of the data to behave erratically due to the display of the data not using the assigned format.
The attached screenshots show the FDS Mapping, field filter selection and the display.
Slice is defined as
{"rows":[{"uniqueName":"Date Price"}],"columns":[{"uniqueName":"[Measures]"}],"measures":[{"uniqueName":"RB","aggregation":"count","grandTotalCaption":"Book"}],"drills":{"rows":[{"tuple":["date price.[2019]"]}]}}
Mapping is as below for the date hierarchy.
"DPyr":{"type":"number","hierarchy":"Date Price","dimensionUniqueName":"Dates","caption":"Year"},"DPmth":{"type":"string","hierarchy":"Date Price","dimensionUniqueName":"Dates","caption":"Month","parent":"DPyr"},"DP":{"type":"date string","hierarchy":"Date Price","dimensionUniqueName":"Dates","caption":"Day","parent":"DPmth"}
⋅ May 18, 2023
Hello,
Thank you for reporting the issue.
We will take a look at the described behavior and provide a fix with our minor release with the ETA June 26th. Our team will notify you about the release.
As a temporary workaround, you can set the "type" of the "DPyr" field as a "string". This way, the dates will be shown correctly.
You are welcome to contact us in case further questions arise.
Kind regards,
Nadia
⋅ June 27, 2023
Hello,
We are happy to let you know that the issue with hierarchy levels that have different data types set in the mapping was fixed.
This is provided in the 2.9.54 version of Flexmonster: https://www.flexmonster.com/release-notes/version-2-9-54/
You are welcome to update the component. Here is our guide on upgrading to the latest version: https://www.flexmonster.com/doc/updating-to-the-latest-version/
Please let us know if the fix works fine for you.
Best Regards,
Maksym
⋅ July 5, 2023
Hello,
Hope you are doing well.
We were wondering if you had a chance to test the updated version. Could you please confirm if the fix works well for you?
Looking forward to hearing your feedback.
Kind regards,
Nadia
⋅ July 25, 2023
Hello,
Hope you're doing well.
Just checking in to ask if you had the opportunity to try out the latest version. Can you please let us know if the issue has been resolved?
Looking forward to hearing from you.
Best regards,
Nadia
⋅ May 3, 2024
Hi Team,
I'm running version 2.9.76 with the recommendation to nominate the year field in the hierarchy as a number. When first running the pivot, it sorts as expected in a low-high format for years (eg. 2010 - 2025)
When drilling into the '+month' however, it reverts to the previous erroneous sort. See attached images.
What we are trying to achieve is the simplest way to transition current reports from a JSON datasource to FDS via the mapping object and slice manipulation. Previously, we were able to define our dates in the 'year/month/day' format via the single mapping line. Now we have added the extra fields to the data for the month and year but are unable to adjust the slice to obtain the previous display.
Previously, the expands for example would use the below method, we cannot get it to work in the new format.
"expands": {
"rows": [ {
"tuple": ["dpl.[2023]"]
}, {
"tuple": ["dpl.[2022].[january]","ccn.[(open position)]"]
}, {
"tuple": ["dpl.[2022].[january]","ccn.[(hedge)]"]
}, {
"tuple": ["dpl.[2022].[february]","ccn.[(open position)]"]
}],
"columns": [{
"tuple": ["rb.[sourcing]"]
}, {
"tuple": ["rb.[trade]"]
}, {
"tuple": ["rb.[iron ore]"]
}]},
⋅ May 3, 2024
Hello,
Thank you for the response.
Our team will look at the described behavior and provide a fix with our minor release with the ETA May 27th. We will notify you about the release.
Feel free to contact us in case other questions arise.
Kind regards,
Nadia
⋅ May 28, 2024
Hello,
We are happy to inform you that the issue with sorting hierarchy members when the child-level members are presorted was fixed.
This fix is available in the 2.9.78 version of Flexmonster: https://www.flexmonster.com/release-notes/version-2-9-78/
You are welcome to update the component. Check out our updating tutorial for guidance: https://www.flexmonster.com/doc/updating-to-the-latest-version/
Please tell us if the fix works. Looking forward to hearing from you.
Kind regards,
Nadia
⋅ June 4, 2024
Hello,
Hope you are doing well.
We were wondering if you had a chance to check the updated version. Please let us know if it works for you.
Looking forward to hearing your feedback.
Kind regards,
Nadia
⋅ June 5, 2024
Hi Nadia,
This looks to have fixed the issue.
Many Thanks.
⋅ June 5, 2024
Hi,
Thank you for the feedback!
You are welcome to contact us if any questions arise.
Kind regards,
Nadia
