Unable to Use conversationId in $search Query for Outlook Messages
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- api
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- TypeScript
- Stars
- 833
- Forks
- 240
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoftgraph/msgraph-sdk-javascript
-
status:waiting-for-triage
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Is anyone here? Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoftgraph/msgraph-sdk-javascript#2005 · 1 reaction ·
-
Is it really correct that the Javascript version of the graph SDK doesn't offer typed requests? Openstatus:waiting-for-triage
Difficulty 5/5 Over a week Newbie friendliness 42/100
-
status:waiting-for-triage type:bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
microsoftgraph/msgraph-sdk-javascript#1999 · 2 comments · 1 reaction ·
-
status:waiting-for-triage type:bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in microsoftgraph/msgraph-sdk-javascript
Similar issues
-
Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenNSW/nsw-srilanka#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
0xMiden/bridge-portal#132 ·
-
react-doctor severity:warning tech-debt
Difficulty 1/5 Under an hour Newbie friendliness 88/100
digidem/comapeo-cloud-app#403 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100