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

API endpoint : custom-fields with multiple filters bug #5515

New Issue
Closed
opened 2025-12-29 19:28:54 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:28:54 +01:00
Owner
Copy Link

Originally created by @Flocon29 on GitHub (Oct 14, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.0.7

Python version

3.8

Steps to Reproduce

  1. Create 2 custom-fields (foo & bar)
  2. Execute HTTP request to API endpoint :
http://netbox_instance:8080/api/extras/custom-fields/?name=foo&name=bar

Expected Behavior

The expected result is the list of all the custom-fields matching with the filters.
Here foo & bar

Observed Behavior

We receive only the last element bar and not both.

Originally created by @Flocon29 on GitHub (Oct 14, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.0.7 ### Python version 3.8 ### Steps to Reproduce 1. Create 2 custom-fields (foo & bar) 2. Execute HTTP request to API endpoint : ```bash http://netbox_instance:8080/api/extras/custom-fields/?name=foo&name=bar ``` ### Expected Behavior The expected result is the list of all the custom-fields matching with the filters. Here `foo` & `bar` ### Observed Behavior We receive only the last element `bar` and not both.
adam added the type: bugstatus: accepted labels 2025-12-29 19:28:54 +01:00
adam closed this issue 2025-12-29 19:28:54 +01:00
adam commented 2025-12-29 19:28:54 +01:00
Author
Owner
Copy Link

@Flocon29 commented on GitHub (Oct 14, 2021):

A discussion has been opened on this subject : https://github.com/netbox-community/netbox/discussions/7543

The behavior for requesting config-contexts is correct :

http://netbox_instance:8080//api/extras/config-contexts/?name=foo&name=bar

But the behavior is not that expected for custom-fields

@Flocon29 commented on GitHub (Oct 14, 2021): A discussion has been opened on this subject : https://github.com/netbox-community/netbox/discussions/7543 The behavior for requesting `config-contexts` is correct : ```bash http://netbox_instance:8080//api/extras/config-contexts/?name=foo&name=bar ``` But the behavior is not that expected for `custom-fields`
adam commented 2025-12-29 19:28:55 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 14, 2021):

Looks like CustomFieldFilterSet doesn't inherit from BaseFilterSet, which is what provides support for multi-value matches as above.

@jeremystretch commented on GitHub (Oct 14, 2021): Looks like CustomFieldFilterSet doesn't inherit from BaseFilterSet, which is what provides support for multi-value matches as above.
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#5515
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?