starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

API filtering 'OR' logic not working when filtering components by device ID #2696

New Issue
Closed
opened 2025-12-29 18:21:10 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:21:10 +01:00
Owner
Copy Link

Originally created by @ajknv on GitHub (Jun 24, 2019).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.6.0

Steps to Reproduce

  1. Issue an API query with filter parameters specifying two different related object IDs, for example:
    https://netbox/api/dcim/interfaces/?device_id=2761&device_id=2762

Expected Behavior

API will return interfaces associated with the devices having ids 2761 and 2762.

Observed Behavior

API returned only the interfaces associated with the last given device id, in this case 2762.

Originally created by @ajknv on GitHub (Jun 24, 2019). ### Environment * Python version: 3.6.8 * NetBox version: 2.6.0 ### Steps to Reproduce 1. Issue an API query with filter parameters specifying two different related object IDs, for example: https://netbox/api/dcim/interfaces/?device_id=2761&device_id=2762 ### Expected Behavior API will return interfaces associated with the devices having ids 2761 and 2762. ### Observed Behavior API returned only the interfaces associated with the last given device id, in this case 2762.
adam added the type: bugstatus: accepted labels 2025-12-29 18:21:10 +01:00
adam closed this issue 2025-12-29 18:21:10 +01:00
adam commented 2025-12-29 18:21:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 24, 2019):

FYI this is because we're employing a method-based filter to also match on devices belonging to the same virtual chassis, so it's not covered by the default MultiValue* filters.

@jeremystretch commented on GitHub (Jun 24, 2019): FYI this is because we're employing a method-based filter to also match on devices belonging to the same virtual chassis, so it's not covered by the default `MultiValue*` filters.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2696
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?