-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Result does not sort correctly with Multiple OrderBy #128
Comments
toddtreece
changed the title
Result does not sort correctly with Multiple OrderBy. (HIGH)
Result does not sort correctly with Multiple OrderBy
Nov 15, 2022
closing this one, but please reopen if i am misunderstanding something. as far as i can tell this seems to be an API bug. here's the request the plugin is sending: {
"componentName": "TabularComponent",
"entityId": "<redacted>",
"maxResults": 200,
"propertyGroupName": "tabularPropertyGroup",
"selectedProperties": [
"total",
"crit"
],
"tabularConditions": {
"orderBy": [
{
"order": "ASCENDING",
"propertyName": "total"
},
{
"order": "ASCENDING",
"propertyName": "total"
}
]
}
} here's the truncated response with incorrect sorting for {
"propertyValues": {},
"tabularPropertyValues": [
[
{
"crit": {
"integerValue": 4
},
"total": {
"integerValue": 0
}
},
{
"crit": {
"integerValue": 5
},
"total": {
"integerValue": 0
}
},
{
"crit": {
"integerValue": 4
},
"total": {
"integerValue": 0
}
}
]
]
} |
scratch that, i think i found the issue. it seems to be a state issue on the frontend that is causing duplicate property names to be sent in the request: {
"order": "ASCENDING",
"propertyName": "total"
},
{
"order": "ASCENDING",
"propertyName": "total"
} |
fixed by #129 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: