The specified sort criteria is invalid. Details: [List]
- Thread starter jutu
- Start date
AlanSidman
Well-Known Member
It would be helpful seeing the data. That being said, I think the problem may be that PQ cannot sort a null value. Maybe change the null to something else, ie. 3 in your if statement.
GraH - Guido
Well-Known Member
My take on the issue.
The order seems to happen on a list object. That can't be sorted it seems. It has nothing to do with the if-statement. The column Name is IsOpen.1 and the sort is done on ServiceOrderTypeNK.
So one of the values in that columns appears to be a list object. I assume the data type should be any. If so mark is a text. Then keep errors. That will give the record or records that have the issue.
How to solve it depends largely on the context. It should best be solved in the semantic model that's the source.
PQ can sort on null values:
EDIT:
Stunningly, PQ can sort mixed values too
And if the whole column is a list the sort order is not accessible via the UI.
Back to start
EDIT 2:
If the column would only contain lists, the error message seems to be different too.
The order seems to happen on a list object. That can't be sorted it seems. It has nothing to do with the if-statement. The column Name is IsOpen.1 and the sort is done on ServiceOrderTypeNK.
So one of the values in that columns appears to be a list object. I assume the data type should be any. If so mark is a text. Then keep errors. That will give the record or records that have the issue.
How to solve it depends largely on the context. It should best be solved in the semantic model that's the source.
PQ can sort on null values:
EDIT:
Stunningly, PQ can sort mixed values too
And if the whole column is a list the sort order is not accessible via the UI.
Back to start
EDIT 2:
If the column would only contain lists, the error message seems to be different too.
Last edited:
GraH - Guido
Well-Known Member
What I can think of is that query folding is going on, since you are using a data model. Meaning the M-code get's translated into SQL. And it hits the fan somehow?
From the field naming it seems to be a key column, which is useable for data modelling. Do you really need to sort on that column? Is there not a dimension for it? I see you also filter after this sorting step. You can try to inverse those steps. Maybe the thing that causes the sort to fail is filter out and the issue is gone that way.
From the field naming it seems to be a key column, which is useable for data modelling. Do you really need to sort on that column? Is there not a dimension for it? I see you also filter after this sorting step. You can try to inverse those steps. Maybe the thing that causes the sort to fail is filter out and the issue is gone that way.
GraH - Guido
Well-Known Member
p45cal, how did you figured that one out?
It's kind of strange that would be the cause for the OP. Look at the code, all is UI default stuff and I surely hope that no-one is going to type in such a long column name from a semantic model.
I'm wondering if the "expand" actions are a potential cause.
Why the sorting is needed, remains a mystery, as we do not see the whole query definition. Without an added index, PQ may well "overwrite" this sorting anyways, so it brings no value at all in many cases.
It's kind of strange that would be the cause for the OP. Look at the code, all is UI default stuff and I surely hope that no-one is going to type in such a long column name from a semantic model.
I'm wondering if the "expand" actions are a potential cause.
Why the sorting is needed, remains a mystery, as we do not see the whole query definition. Without an added index, PQ may well "overwrite" this sorting anyways, so it brings no value at all in many cases.