Dynamics Community Forum Thread Details

Dynamics sales, search contacts api error "The query parameter [REDACTED] is not supported"

Hi everyone,

We’ve integrated Dynamics Sales (CRM) into our web app, and one of the APIs we use is the Search Contacts API including when using the $filter query parameter along with contains() method, it works fine generally.
However, for one of our customers, when they try to search contacts using the same API with a $filter query, it returns this error:

“The query parameter [REDACTED] is not supported”

Note: The word [REDACTED] is returned exactly like this—I didn’t modify the message.

This works fine for all other customers, and I’m unable to reproduce it in our dev environment.
Any idea what might cause this error in a specific CRM environment?
I am wondering if this could be a limitation or setting in the customer’s Dynamics environment?

Would really appreciate any insights or suggestions for how to debug this further. Thanks in advance! 🙏

Here is the original request:

{
"status": 400,
"method": "GET",
"url": "org_url/api/data/v9.2/contacts?$filter=contains(yomifullname,'REPLACED CUSTOMER DATA WITH THIS')",
"headers": {
"cache-control": "no-cache",
"allow": "OPTIONS,GET,HEAD,POST",
"content-type": "application/json; odata.metadata=minimal",
"expires": "-1",
"strict-transport-security": "max-age=31536000; includeSubDomains",
"x-content-type-options": "nosniff",
"odata-version": "4.0",
"date": "Thu, 13 Mar 2025 20:13:56 GMT",
"content-length": "91",
"x-ms-service-request-id": "fe3e1f64-f964-4b2c-b7f1-a9afb24ad40a",
"x-ms-ratelimit-time-remaining-xrm-requests": "1,200.00",
"x-ms-ratelimit-burst-remaining-xrm-requests": "7999"
},
"body": {
"error": {
"code": "0x80060888",
"message": "The query parameter [REDACTED] is not supported"
}
}
}

Categories:

Dynamics 365 Sales

Microsoft Dynamics CRM

Hi there! Good morning, evening, or afternoon - depending on where you are :) Hope you are well today!

Hopefully you've solved this by now - I see it was posted last week :)

If not, dropping some ideas here:

Possible Causes and Suggestions:
- Unpublished Customizations or Metadata Changes:
  - If the customer's environment has customizations related to the yomifullname field, ensure these are properly published. Sometimes metadata changes aren't fully applied until they are published in Dynamics.
- Missing Permissions or Security Settings:
  - It's worth checking if the customer’s user role has proper permissions to access the yomifullname field or if the field is restricted in their environment. This can lead to unexpected errors when querying with $filter.
- Environment-Specific Limitations:
  - Sometimes, custom entities, fields, or attribute configurations might behave differently between environments. Validate that yomifullname is set as searchable and included in the entity's Quick Find view under the customization settings.
- CRM Version Differences or Updates:
  - It could also be related to a version mismatch—confirm that the customer’s CRM environment is running the same version and update level as your development environment. If they have a slightly older version, some query features might behave differently.
- Data-Specific Issues:
  - There may be specific data records in the customer's environment that trigger this issue. For example, special characters or malformed data in the yomifullname field could cause the $filter query to fail.
- API Restrictions or Overrides:
  - Certain APIs might have restrictions based on organization-specific configurations. Verify the API call works for other entities or fields in the customer's environment to rule out broader issues.
Debugging Steps:
- Replicate in a Test Instance:
  - If possible, replicate the customer’s settings in a sandbox environment to see if the issue can be reproduced there.
- Inspect Field Metadata:
  - Use the EntityDefinitions and AttributeMetadata API calls to retrieve metadata about the yomifullname field and confirm that it supports contains() and $filter.
- Perform a Broader Query:
  - Try running the query with a simpler $filter parameter or another method like startswith() to isolate whether contains() specifically is causing the issue.
- Enable Plugin Trace Logs:
  - If the customer has custom plugins or workflows, enable trace logs to check for errors or conflicts when the query is run.

Quick Links