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 GET /api/dcim/devices with site and site__n not working properly #9239

New Issue
Closed
opened 2025-12-29 20:47:23 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:47:23 +01:00
Owner
Copy Link

Originally created by @jayGG83 on GitHub (Feb 13, 2024).

Deployment Type

netbox-docker

NetBox Version

v3.7.1

Python Version

3.10

Steps to Reproduce

  1. Create a Site
  2. Create a device type
  3. Create a device and assign to the site
  4. Execute /api/dcim/devices/?site={site_name}
  5. Execute /api/dcim/devices/?site={site_slug}
  6. Execute /api/dcim/devices/?site__n={site_slug}

Expected Behavior

Expected behavior
Step 4: Return the information regarding the devices in site based on the site name
Step 5: It should return an error stating that the site value provided is not one of the available choices, as we provided the slug name instead of the site name
Step 6: Return the information regarding the devices in site based on the slug name

Observed Behavior

Step 4: Returned:

{
  "site": [
    "Select a valid choice. {site_name} is not one of the available choices."
  ]
}

Step 5: Returned a valid result. Attribute site accepts the slug name instead of the site name.
Step 6: Returned all existing devices from all sites

Originally created by @jayGG83 on GitHub (Feb 13, 2024). ### Deployment Type netbox-docker ### NetBox Version v3.7.1 ### Python Version 3.10 ### Steps to Reproduce 1. Create a Site 2. Create a device type 3. Create a device and assign to the site 4. Execute ```/api/dcim/devices/?site={site_name}``` 5. Execute ```/api/dcim/devices/?site={site_slug}``` 6. Execute ```/api/dcim/devices/?site__n={site_slug}``` ### Expected Behavior Expected behavior Step 4: Return the information regarding the devices in site based on the site name Step 5: It should return an error stating that the site value provided is not one of the available choices, as we provided the slug name instead of the site name Step 6: Return the information regarding the devices in site based on the slug name ### Observed Behavior Step 4: Returned: ```json { "site": [ "Select a valid choice. {site_name} is not one of the available choices." ] } ``` Step 5: Returned a valid result. Attribute site accepts the slug name instead of the site name. Step 6: Returned all existing devices from all sites
adam closed this issue 2025-12-29 20:47:23 +01:00
adam commented 2025-12-29 20:47:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 13, 2024):

These filters are working as expected.

  • ?site={site_name} is not a valid query, as the site filter matches against the slug, not the name
  • ?site={site_slug} works as expected, returning only the devices assigned to the specified site
  • ?site__n={site_slug} works as expected, returning only the devices not assigned to the specified site
@jeremystretch commented on GitHub (Feb 13, 2024): These filters are working as expected. * `?site={site_name}` is not a valid query, as the `site` filter matches against the slug, not the name * `?site={site_slug}` works as expected, returning only the devices assigned to the specified site * `?site__n={site_slug}` works as expected, returning only the devices _not_ assigned to the specified site
adam commented 2025-12-29 20:47:24 +01:00
Author
Owner
Copy Link

@jayGG83 commented on GitHub (Feb 13, 2024):

Thanks for the info. Now I see the pattern that I didn't saw before. So any attribute with __n means not in?

@jayGG83 commented on GitHub (Feb 13, 2024): Thanks for the info. Now I see the pattern that I didn't saw before. So any attribute with __n means not in?
adam commented 2025-12-29 20:47:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 13, 2024):

Yeah, the n is a lookup modifier which negates the query. It works similarly to __gt (greater than) and __lt (less than) for numeric fields.

@jeremystretch commented on GitHub (Feb 13, 2024): Yeah, the `n` is a lookup modifier which negates the query. It works similarly to `__gt` (greater than) and `__lt` (less than) for numeric fields.
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
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#9239
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?