Documents order in query results

Hello,

I have this question from Christophe Richard from Oceane Consulting who wants to know why this query results retrieve documents in a different order than the one passed in the parameters query.

Can you please help him?
Thanks

Bonjour,
Notre requête est passée via un appel de votre API en passant par une classe JAVA.
Voici la requête que nous envoyons :

GET https://myocdmcms.cdn.prismic.io/api/v1/documents/search?integrationFieldsRef=myocdmcms~383f09ae-4db8-4523-aa9b-7b3dc4e9c467 {access_token=*** q=[[:d = at(document.type, "article")][:d = in(document.id, ["WwbiiyoAACoAlXGg","WmBp7SkAALVG056M","WuHaxCkAAAWd6Ted","Wxksjx0AAKKI30CU","Wr3pmSYAACUAMMyW","WsOEGyYAACMASXvT","WsOEYyYAACUASX0Y","WnAxvioAAIvo9YeS","WnGKBB4AAL1cfU7e","Wr0ZLSYAACMALTUd","WmCerikAALBL1Ihl","Wr3qhCYAACYAMNC4","Wx-aYykAAJBg-4pp","WmCmMykAAK5L1Km5","WnBFsB4AAF0Cd7Fh","Wr0Y2SYAACYALTOm","Wr3p2yYAACMAMM2_"])]] ref=YCOjtxIAACIARJyV pageSize=12 page=1}

La réponse renvoi la liste des documents mais pas dans l'ordre défini via la liste d'ID de documents passée en paramètre.
En faisant quelques tests, je me suis aperçu que si j'enlève les paramètres de pagination ("pageSize" et "page"), le résultat est bon. Il semble donc que les documents sont mal triés si l'on renseigne ces paramètres.

N.B. : Ce message est également dans le chatbot.
Cordialement.

Hey Antoine,

The in predicate should indeed return the documents in the correct order, so I'm not sure why this is happening. I'm going to submit an issue ticket. I'll let you know what happens :slight_smile:

Sam

I recreated this issue on one of my own repos. I'll let you know what the dev team says.

Hey Sam,
Can you tell me when this issue will be patched ? Please

May we have more information about this issue.

Hi @crichard ,

Sorry for the delayed response. I know that the dev team is tracking this issue, but I'll sync with them to get more information and let you know what I find out.

Sam

Hi @crichard and @antoine.gilbert ,

I synced with our dev team on this, and they're actively looking in to it. I'll let you know when I have an update :slight_smile:

Sam

Hi Sam,
Ok, thanks
Christophe

1 Like

Hi Sam,
Still no news ?

Hey @crichard ,

Thanks for following up. I know that one of our devs was working on it this week, but didn't get to the bottom of it. I'll follow up with the team to see how it's moving along.

Sam

Hey @crichard ,

I just checked in with the dev team, and this is on their list of priorities, but they probably won't get back to it for a few weeks. I'll let you know when I have more info.

Sam

Hi Sam,
Have you some news. This correction is taking a while.
Christophe

Hi @crichard ,

I checked in with the dev team, and they are working on the issue. I'll let you know when I have more info.

Best,
Sam

Hi Sam,
Some news ?
Do you know when correction will be in production ?
It's time we have a correction.
Christophe

Hey @crichard ,

Sorry for the silence on my end. This issue is still prioritized by the dev team, but I haven't heard anything about it in a little while. I'll follow up with them to see if they have any updates.

Sam

Hi @crichard ,

I followed up with the dev team, and I wish I could give a more concrete response, but for now this is still queued up as a priority item. It will be addressed, but I can't say for sure when.

Sam

Hi @samlittlefair
Have you some news ?
The corrections is in production ?
Christophe

Hey @crichard ,

Sorry for the silence on my end. I checked in with the dev team, and they said that this is still prioritized. Sorry I can't give more detail. Do you need help with a workaround in the meantime?

Sam

Sam,
I don't know how it's work in prismic company, but i'm surprised this correction has not been already installed in production. We have discovered this bug for six month. Why does it take such a long time ? We have been patient until now, but can you pleased try to quicken the process of correction. We don't want to use a workaround.
Christophe