Filtering for Custom Field #9379

Closed
opened 2025-12-29 20:49:09 +01:00 by adam · 2 comments
Owner

Originally created by @Creepios on GitHub (Mar 22, 2024).

NetBox version

v3.7.4

Feature type

Change to existing functionality

Proposed functionality

Add filtering for custom fields. This doesnt work currently. Was already mentioned in Discussion #7907
Especially string fields should be possible to be filtered.

Use case

My own example is that I have some custom field with an seperate string id for a device type which I would like to filter for via API with exact matching.

Database changes

No response

External dependencies

No response

Originally created by @Creepios on GitHub (Mar 22, 2024). ### NetBox version v3.7.4 ### Feature type Change to existing functionality ### Proposed functionality Add filtering for custom fields. This doesnt work currently. Was already mentioned in Discussion #7907 Especially string fields should be possible to be filtered. ### Use case My own example is that I have some custom field with an seperate string id for a device type which I would like to filter for via API **with exact matching**. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:49:09 +01:00
adam closed this issue 2025-12-29 20:49:09 +01:00
Author
Owner

@jeremystretch commented on GitHub (Mar 22, 2024):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Mar 22, 2024): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
Author
Owner

@jeremystretch commented on GitHub (Apr 3, 2024):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@jeremystretch commented on GitHub (Apr 3, 2024): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9379