Error when using orderby

Rizwan Ansari 91

Dear Experts,

I am calling sharepoint rest api using graph,

https://graph.microsoft.com/v1.0/sites/{site-id}/lists/{list-id}/items?expand=fields(select=Title)&$orderby=fields/SortOrder

Added the column to index also added

'Prefer: HonorNonIndexedQueriesWarningMayFailRandomly'

in header.

but getting error in response:

{
    "error": {
        "code": "invalidRequest",
        "message": "Field 'SortOrder' cannot be referenced in filter or orderby as it is not indexed. Provide the 'Prefer: HonorNonIndexedQueriesWarningMayFailRandomly' header to allow this, but be warned that such queries may fail on large lists.",
        "innerError": {
            "date": "2023-09-04T07:34:20",
            "request-id": "32b25e8a-38c8-45b4-a377-f95c39e0dd87",
            "client-request-id": "32b25e8a-38c8-45b4-a377-f95c39e0dd87"
        }
    }
}

Francesco Laserpe 5 Reputation points

2023-09-04T09:05:00.8833333+00:00

same problem in the last days
Adam Bryant 0 Reputation points

2023-09-04T13:09:08.7033333+00:00

Anyone's tenant working again yet, I have had to code round this by filtering on the full list, thankfully there are only around 300 items

Accepted answer

RaytheonXie_MSFT 36,651 Reputation points Microsoft Vendor

2023-09-04T09:01:30.37+00:00

Hi @Rizwan Ansari @Iginio Colangelo,

Per your descriptions, there might be some issues in the backend of Graph api. As a workaround, I will suggest you to raise a support in Microsoft Azure. You can report this bug to Microsoft and get a response within one business day usually.
Please sign in to rate this answer.

1 person found this answer helpful.
RaytheonXie_MSFT 36,651 Reputation points Microsoft Vendor

2023-09-05T05:55:46.3766667+00:00

Hi @Rizwan Ansari

Since the Microsoft have fixed the issue, could you please kindly click "Accept Answer". It would be helpful to others who have similar issue in the future.

Andrei Iuresi 5 Reputation points

2023-09-05T12:55:52.1066667+00:00

I have the same error since 4 September. On 1 September 2023 the system was functional. "error":{"code":"invalidRequest","message":"Field 'Task_Id' cannot be referenced in filter or orderby as it is not indexed. Provide the 'Prefer: HonorNonIndexedQueriesWarningMayFailRandomly'}} I mention that I have index on Task_Id column and send request in header with HonorNonIndexedQueriesWarningMayFailRandomly.

"&filter=fields/Task_Id eq {$task->id}"
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

4 additional answers

Garcia Argüez, Javier 15 Reputation points

2023-09-04T08:30:15.3166667+00:00

I have the same problem, the app has stop working this weekend. I have tried in MS Graph with different lists and documents libraries and have the same error. And the fields are indexed a long time ago.
Please sign in to rate this answer.

1 person found this answer helpful.
Rizwan Ansari 91 Reputation points

2023-09-04T08:33:23.83+00:00

I have two different tenant, on 1 tenant its working and 2 not working.please let me know if you found any solution.

Iginio Colangelo 35 Reputation points

2023-09-04T08:34:36.3133333+00:00

Hi at all, we have the same problem, too. It seems the problem occurs when in graph api you use "filter" or "orderby" function.

Garcia Argüez, Javier 15 Reputation points

2023-09-04T09:21:45.5766667+00:00

Rizwan, i have two tenants too and on tenant 1 not working but on tenant 2 yes... Same query, same list with the same indexed fields.

Rizwan Ansari 91 Reputation points

2023-09-04T09:24:40.1466667+00:00

Me too facing same error, i have open support ticket with MS let us wait for the solution.

Iginio Colangelo 35 Reputation points

2023-09-04T09:33:22.1833333+00:00

@Rizwan Ansari I've opened a ticket, too. Please update into this topic if you have news. We continue receiving complains. I'll do the same. Regards

Rizwan Ansari 91 Reputation points

2023-09-04T09:38:06+00:00

Sure i will update

Andrei Iuresi 5 Reputation points

2023-09-05T13:55:16.52+00:00

me too
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Bayraktar, Aytac 5 Reputation points

2023-09-05T13:48:24.9066667+00:00
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
RaytheonXie_MSFT 36,651 Reputation points Microsoft Vendor

2023-09-04T08:38:19.51+00:00
Hi @Rizwan Ansari,

Per my test, query parameter $orderby can be applied on the expanded properties of fieldvalueset, and usage of the is not recommended large lists. Please refer to following

https://graph.microsoft.com/v1.0/sites/{site-id}/lists/{list-id}/items?$expand=fields&$orderby=fields/SortOrder desc Prefer: HonorNonIndexedQueriesWarningMayFailRandomly

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
Iginio Colangelo 35 Reputation points

2023-09-04T08:44:35.0166667+00:00

In our case, we have a list with 80 elements ( not too much ) and when we use "filter" or "orderby" functions we received "Error: Field 'XXXXXXXX' cannot be referenced in filter or orderby as it is not indexed. Provide the 'Prefer: HonorNonIndexedQueriesWarningMayFailRandomly' header to allow this, but be warned that such queries may fail on large lists".
By putting in Header "Prefer: HonorNonIndexedQueriesWarningMayFailRandomly" nothing changes and we receive the same error. It happens in 2 different tenants. The same adding an index in the column.

I think for rizwan ansari is the same.

Thanks for your help

Rizwan Ansari 91 Reputation points

2023-09-04T08:45:13.26+00:00

Hi Raytheon,

The api was working fine till yesterday.

Garcia Argüez, Javier 15 Reputation points

2023-09-04T08:51:55.76+00:00

This is another try, and i have the same problem:

The column is indexing and the list have 25 items.

Iginio Colangelo 35 Reputation points

2023-09-04T11:15:14.2+00:00

Hi @Rizwan Ansari , no good news. I hope they will fix it soon. I received this answer as follows :
Title: Users may be unable to filter list items using Microsoft Graph API in SharePoint Online User impact: Users may be unable to filter list items using Microsoft Graph API in SharePoint Online.
Current status: We've identified that a recent standard service update, inadvertently contains a code regression which is causing users attempting to filter list items using Microsoft Graph API in SharePoint Online to encounter failures. We've developed a fix to repair the code regression and we're conducting extensive validation checks to ensure its efficacy. Once the fix is validated, we'll begin deploying it to the affected infrastructure to remediate impact. Scope of impact: Impact is specific to some users attempting to list items using Microsoft Graph API in SharePoint Online.
Root cause: A recent standard service update, inadvertently contains a code regression which is causing users

Garcia Argüez, Javier 15 Reputation points

2023-09-04T11:19:35.13+00:00

Thanks a lot!!

Rizwan Ansari 91 Reputation points

2023-09-04T11:46:44.87+00:00

Thanks for update..

el-chupacabra 0 Reputation points

2023-09-04T16:06:44.61+00:00

Hello, we happen to have the same issue. Do you have any news ?

Rizwan Ansari 91 Reputation points

2023-09-05T05:07:58.37+00:00

Hello friends, Filter and OrderBy started working :)
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Chetan Kolhari 0 Reputation points

2023-09-05T05:42:27.2866667+00:00

I have customer complains about having the same issue in their tenants from yesterday. So far any progress from Microsoft anyone heard?
Please sign in to rate this answer.
Adam Bryant 0 Reputation points

2023-09-05T05:51:28.74+00:00

Seems to be working again now

Iginio Colangelo 35 Reputation points

2023-09-05T06:52:07.73+00:00

It seems working again for me,too

Chris Laird 6 Reputation points

2023-09-05T13:30:25.73+00:00

Still not working for me. I've tried deleting and re-creating the index on the relevant columns but still getting the same error. Adding the suggested header makes no difference.

Query URL: https://graph.microsoft.com/v1.0/sites/{site-id}/lists/{list-id}/items?expand=fields&$filter=fields/ClientCode eq 'A1002'

Error:

{ error: { code: 'invalidRequest', message: "Field 'ClientCode' cannot be referenced in filter or orderby as it is not indexed. Provide the 'Prefer: HonorNonIndexedQueriesWarningMayFailRandomly' header to allow this, but be warned that such queries may fail on large lists.", innerError: { date: '2023-09-05T13:22:25', 'request-id': '66bc019a-3be0-4180-8746-3db8105cf817', 'client-request-id': '66bc019a-3be0-4180-8746-3db8105cf817' } } }

Chetan Kolhari 0 Reputation points

2023-09-06T04:38:21+00:00

Same goes with my customer. It works intermittent though. I have raised a MS ticket, let's see what they have to say.

Chetan Kolhari 0 Reputation points

2023-09-06T04:41:14.4466667+00:00

It doesn't work either in our case. It started to work intermittent though.

Raised a MS ticket, will post the update, once I hear more on this.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Error when using orderby

4 additional answers

Your answer