8000 Site `search` query parameter is inconsistent between SDK and Graph Explorer · Issue #2346 · microsoftgraph/msgraph-sdk-java · GitHub
[go: up one dir, main page]

Skip to content
Site search query parameter is inconsistent between SDK and Graph Explorer #2346
@rocketraman

Description

@rocketraman

Describe the bug

When using Graph Explorer, the API endpoint https://graph.microsoft.com/v1.0/sites returns nothing.

With Graph Explorer, it appears that using ?search=* works to return all sites.

When using the SDK, the same endpoint returns sites, and specifying queryParameters.search = "*" throws:

Syntax error: character '*' is not valid at position 0 in '*'.
com.microsoft.graph.models.odataerrors.ODataError: Syntax error: character '*' is not valid at position 0 in '*'.

based on the response:

{
  "error": {
    "code": "BadRequest",
    "message": "Syntax error: character '*' is not valid at position 0 in '*'.",
    "innerError": {
      "date": "2025-03-31T18:56:12",
      "request-id": "f29db1f9-b0d7-4d4b-a724-7599a932bcca",
      "client-request-id": "fb1f170c-a4c0-4eb6-bb8c-852e3d3c7762"
    }
  }
}

These inconsistencies (along with issues like #2344 and #2345 ) make it very difficult to sanely develop applications using the MS Graph SDK.

One difference is that I am using cl 60A2 ient cert / secret credentials for the SDK and personal credentials for Explorer. That should not affect the API's functional behavior though.

Expected behavior

APIs should have consistent behavior.

How to reproduce

See above.

SDK Version

6.33.0

Latest version known to work for scenario above?

No response

Known Workarounds

Pull out hair, write code with many "argh" comments, and proceed

Debug output

No response

Configuration

No response

Other information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    status:waiting-for-triageAn issue that is yet to be reviewed or assignedtype:bugA broken experience

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0