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

Custom Field and Allow Import To Custom Field #1437

New Issue
Closed
opened 2025-12-29 16:32:11 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:32:11 +01:00
Owner
Copy Link

Originally created by @hmmxp on GitHub (Dec 5, 2017).

Issue type

[Y] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 3.4
  • NetBox version: 2.2.6

Description

Default Add a new circuit have the following fields:

Circuit

  • Provider
  • Circuit ID
  • Type
  • Activation Date
  • Commit rate (Kbps)
  • Description

Tenancy

  • Tenant group
  • Tenant

Currently have added custom fields such as contract end date. MRC and such.

As we have a lot of circuits and having the additional custom fields will allow for us to manage the circuits with ease, to use Circuit import function to import all the circuit information including both the default fields and custom fields.

Originally created by @hmmxp on GitHub (Dec 5, 2017). <!-- Before opening a new issue, please search through the existing issues to see if your topic has already been addressed. Note that you may need to remove the "is:open" filter from the search bar to include closed issues. Check the appropriate type for your issue below by placing an x between the brackets. For assistance with installation issues, or for any other issues other than those listed below, please raise your topic for discussion on our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please note that issues which do not fall under any of the below categories will be closed. Due to an excessive backlog of feature requests, we are not currently accepting any proposals which extend NetBox's feature scope. Do not prepend any sort of tag to your issue's title. An administrator will review your issue and assign labels as appropriate. ---> ### Issue type [Y] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) If you are submitting a bug report and have made any changes to the code base, please first validate that your bug can be recreated while running an official release. --> ### Environment * Python version: 3.4 * NetBox version: 2.2.6 <!-- BUG REPORTS must include: * A list of the steps needed for someone else to reproduce the bug * A description of the expected and observed behavior * Any relevant error messages (screenshots may also help) FEATURE REQUESTS must include: * A detailed description of the proposed functionality * A use case for the new feature * A rough description of any necessary changes to the database schema * Any relevant third-party libraries which would be needed --> ### Description Default Add a new circuit have the following fields: Circuit - Provider - Circuit ID - Type - Activation Date - Commit rate (Kbps) - Description Tenancy - Tenant group - Tenant Currently have added custom fields such as contract end date. MRC and such. As we have a lot of circuits and having the additional custom fields will allow for us to manage the circuits with ease, to use Circuit import function to import all the circuit information including both the default fields and custom fields.
adam closed this issue 2025-12-29 16:32:11 +01:00
adam commented 2025-12-29 16:32:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 30, 2018):

Thank you for your interest in NetBox. It looks like your feature request is missing some information. Per the contributing guidelines, please ensure that you have provided all of the following:

  • A detailed description of the proposed functionality
  • A use case for the feature; who would use it and what value it would add to NetBox
  • A rough description of changes necessary to the database schema (if applicable)
  • Any third-party libraries or other resources which would be involved

Please update the issue so that it meets all of these requirements. If no response is received within a week, this issue will be closed. Thanks!

@jeremystretch commented on GitHub (Jan 30, 2018): Thank you for your interest in NetBox. It looks like your feature request is missing some information. Per the [contributing guidelines](https://github.com/digitalocean/netbox/blob/develop/CONTRIBUTING.md), please ensure that you have provided all of the following: * A detailed description of the proposed functionality * A use case for the feature; who would use it and what value it would add to NetBox * A rough description of changes necessary to the database schema (if applicable) * Any third-party libraries or other resources which would be involved Please update the issue so that it meets all of these requirements. If no response is received within a week, this issue will be closed. Thanks!
adam commented 2025-12-29 16:32:12 +01:00
Author
Owner
Copy Link

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

Closing this issue as it does not meet the standards listed above. See #1844 for other discussion regarding the import of custom fields.

@jeremystretch commented on GitHub (Feb 13, 2018): Closing this issue as it does not meet the standards listed above. See #1844 for other discussion regarding the import of custom fields.
adam commented 2025-12-29 16:32:12 +01:00
Author
Owner
Copy Link

@Here2Tinker commented on GitHub (Nov 9, 2018):

Hello,

Newbie here, GitHub and NetBox wise so please be patient, I am just getting to know the community and the product. :-)

As proposed, I have seen #1844 but it's about migrating custom fields between different instances of NetBox - where as my perdicament is centered around importing a lot of information from a CSV file.

So far I've tested it on our NetBox (version v2.4.3) by using the standard import column headers:

device_role,manufacturer,model_name,status,site

This works fine.

Then, I have added several custom fields for Devices and extended the column headers accordingly:

device_role,manufacturer,model_name,status,site,management_ip,environment_tag,business_impact,pci_device,tech_owner

However, the test import fails as soon as it reaches the 1st custom field name:
Unexpected column header "management_ip" found.

Do I need to provide more details in the column headers? Like, database table holding the custom fields so it doesn't query the default one?

Please find below the issue details, to the best of my knowledge:

  • Detailed description of the proposed functionality
    Possibility to add through UI all the pre-created custom fields to column header (for Devices import)
  • Use case for the feature; who would use it and what value it would add to NetBox:
    Easier import od devices from 3rd party CMDB
  • A rough description of changes necessary to the database schema (if applicable)
    None required, I think?
  • Any third-party libraries or other resources which would be involved
    Also, none?

Regards,
Igor

@Here2Tinker commented on GitHub (Nov 9, 2018): Hello, Newbie here, GitHub and NetBox wise so please be patient, I am just getting to know the community and the product. :-) As proposed, I have seen #1844 but it's about migrating custom fields between different instances of NetBox - where as my perdicament is centered around importing a lot of information from a CSV file. So far I've tested it on our NetBox (version v2.4.3) by using the standard import column headers: _device_role,manufacturer,model_name,status,site_ This works fine. Then, I have added several custom fields for Devices and extended the column headers accordingly: _device_role,manufacturer,model_name,status,site,**management_ip,environment_tag,business_impact,pci_device,tech_owner**_ However, the test import fails as soon as it reaches the 1st custom field name: **Unexpected column header "management_ip" found.** Do I need to provide more details in the column headers? Like, database table holding the custom fields so it doesn't query the default one? Please find below the issue details, to the best of my knowledge: - Detailed description of the proposed functionality Possibility to add through UI all the pre-created custom fields to column header (for Devices import) - Use case for the feature; who would use it and what value it would add to NetBox: Easier import od devices from 3rd party CMDB - A rough description of changes necessary to the database schema (if applicable) None required, I think? - Any third-party libraries or other resources which would be involved Also, none? Regards, Igor
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#1437
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?