Unable to Use conversationId in $search Query for Outlook Messages
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 15/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- typescript
- Área
- api
Línea de trabajo
Start by reproducing the exact /me/messages request in Graph Explorer, including the conversationId, date, to, and from filters. Compare the result with the reported behavior and determine whether the limitation is in the TypeScript SDK or the Outlook API; done means identifying an actionable SDK change or confirming that the service does not support this query.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Bug Report
Prerequisites
- Can you reproduce the problem?
- Are you running the latest version?
- Are you reporting to the correct repository?
- Did you perform a cursory search?
For more information, see the CONTRIBUTING guide.
Description
I am encountering an issue with the Outlook API when trying to use the conversationId parameter in a $search query for email messages.
Console Errors: None
Screenshots: None
Steps to Reproduce
Attempt to retrieve email messages using the /me/messages endpoint.
Utilize a $search query that includes the conversationId parameter, as demonstrated below:
/me/messages?$search="(to:${userEmail} OR from:${userEmail}) AND conversationId:${id} AND received>=${startDate} AND received<=${endDate}"
Observe that the query does not produce the desired results due to the inability to use conversationId with $search.
Expected behavior: I expect to be able to construct a query that enables me to retrieve email messages based on the conversationId parameter using the $search operator.
Actual behavior: The conversationId parameter cannot be effectively employed within a $search query for email message retrieval.
Additional Context
- The capability to create sophisticated queries is crucial for efficient email message retrieval.
- This issue may affect users who rely on precise filtering and querying of email messages.
- A similar issue was discussed in this thread: Link to Discord Thread
Usage Information
Request ID - Value of the requestId field if you are receiving a Graph API error response
This request doesn't work even in Graph Explorer!
SDK Version: "@microsoft/microsoft-graph-client": "^3.0.6",
Node Version: "@types/node": "^20.3.1", "ts-node": "^10.9.1",
Browser Name: N/A
Version: N/A
- Lenguaje dominante
- TypeScript
- Estrellas
- 833
- Forks
- 240
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoftgraph/msgraph-sdk-javascript
-
status:waiting-for-triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
-
Is anyone here? Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
microsoftgraph/msgraph-sdk-javascript#2005 · 1 reacción ·
-
Is it really correct that the Javascript version of the graph SDK doesn't offer typed requests? Abiertostatus:waiting-for-triage
Dificultad 5/5 Más de una semana Aptitud para principiantes 42/100
-
status:waiting-for-triage type:bug
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
microsoftgraph/msgraph-sdk-javascript#1999 · 2 comentarios · 1 reacción ·
-
status:waiting-for-triage type:bug
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
Todos los issues de microsoftgraph/msgraph-sdk-javascript
Issues similares
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
dennys-bd/agent-hive#184 ·
-
Add: hunch Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
AbdelStark/awesome-typesafe#104 ·
-
ai-observability bug team/ai-observability
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
vicharanashala/fln#563 ·