Skip to content

Fix: return Yes/No field values as integers in search (GLPI 11) - #1302

Open
Rom1-B wants to merge 1 commit into
11.0/bugfixesfrom
support_46929_11
Open

Rom1-B wants to merge 1 commit into
11.0/bugfixesfrom
support_46929_11

Conversation

@Rom1-B

@Rom1-B Rom1-B commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

Checklist before requesting a review

Please delete options that are not relevant.

  • I have performed a self-review of my code.
  • I have added tests (when available) that prove my fix is effective or that my feature works.
  • I have updated the CHANGELOG with a short functional description of the fix or new feature.
  • This change requires a documentation update.

Description

  • It fixes !46929
  • Since 1.24.6, Yes/No field values returned by the search engine (including the REST API search endpoint) are strings "0"/"1" instead of integers 0/1.
  • Scripts relying on a truthy check now treat "0" as true, which breaks integrations that worked with 1.24.5.
  • The default value applied in search results for Yes/No fields is now an integer, restoring the previous value type.

Screenshots (if appropriate):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants