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

Custom Sorting is not working for 'Member' with custom data source API

Answered
Parmod asked on October 6, 2020

Hi, there is some issue is flexmonster custom data source API
my ‘members’ request response is:

//Field response
{
"fields": [
{
"uniqueName": "Custom Day Of Week",
"type": "string",
"caption": "Custom Day Of Week"
},
{
"uniqueName": "Custom Month",
"type": "string",
"caption": "Custom Month"
},
{
"uniqueName": "Weight",
"type": "number",
"caption": "Weight"
}
],
"aggregations": {
"any": [
"count",
"distinctcount"
],
"date": [
"count",
"distinctcount",
"min",
"max"
],
"number": [
"sum",
"average",
"count",
"distinctcount",
"min",
"max"
]
},
"filters": {
"date": {
"members": true,
"query": [
"equal",
"not_equal",
"after",
"after_equal",
"before",
"before_equal",
"between",
"not_between",
"last",
"current",
"next"
],
"valueQuery": [
"equal",
"not_equal",
"greater",
"greater_equal",
"less",
"less_equal",
"between",
"not_between"
]
},
"number": {
"members": true,
"query": [
"equal",
"not_equal",
"greater",
"greater_equal",
"less",
"less_equal",
"between",
"not_between"
],
"valueQuery": [
"equal",
"not_equal",
"greater",
"greater_equal",
"less",
"less_equal",
"between",
"not_between"
]
},
"string": {
"members": true,
"query": [
"equal",
"not_equal",
"begin",
"not_begin",
"end",
"not_end",
"contain",
"not_contain",
"greater",
"greater_equal",
"less",
"less_equal",
"between",
"not_between"
],
"valueQuery": [
"equal",
"not_equal",
"greater",
"greater_equal",
"less",
"less_equal",
"between",
"not_between"
]
},
"advanced": true
}
}
// 1st members response
{
"members": [
{
"value": "January",
"id": "1"
},
{
"value": "July",
"id": "7"
},
{
"value": "August",
"id": "8"
},
{
"value": "September",
"id": "9"
},
{
"value": "December",
"id": "12"
}
],
"sorted": true,
"page": 0,
"pageTotal": 1
}
//2nd memmbers response
{
"members": [
{
"value": "Sunday",
"id": "0"
},
{
"value": "Monday",
"id": "1"
},
{
"value": "Tuesday",
"id": "2"
},
{
"value": "Wednesday",
"id": "3"
},
{
"value": "Thursday",
"id": "4"
},
{
"value": "Friday",
"id": "5"
},
{
"value": "Saturday",
"id": "6"
}
],
"sorted": true,
"page": 0,
"pageTotal": 1
}

From server I’m sending the value of ‘sorted’ as true.
Still on the client(flexmonsterjs) the member are shown as alpha-sorted

Please see the attach screenshot.

Attachments:
SortingProblem..PNG

2 answers

Public
Vera Didenko Flexmonster October 7, 2020

Hello, 
 
Thank you for reaching out to us. 
 
We would like to confirm that this is not the expected behavior: if sorted is set as true, the members’ order from the response should be used as AZ order on the UI.
Our team will provide the fix to this issue in the minor release version with the ETA 2nd of November.
 
In the meantime, as a workaround, we kindly suggest setting the defaultHierarchySortName option to "unsorted", for example:

var pivot = new Flexmonster({
container: "#pivot-container",
componentFolder: "https://cdn.flexmonster.com/",
toolbar: true,
report: {
options: {
defaultHierarchySortName: "unsorted"
},
dataSource: {...}
...
}
});

 
Please let us know if this works for you.
Looking forward to your response. 
 
Kind regards, 
Vera

Public
Parmod October 7, 2020

thank you!, I have already tried setting the defaultHierarchySortName option earlier to "unsorted". It worked 90 percent as expected.

Please login or Register to Submit Answer