-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Netbox v3.7.6's Interface's exported CSV can't be re-imported with the device name changed to another existing device: errors: header name case mismatch and invalid type choice #16190
Comments
This is a deliberate design decision by the NetBox developers, and they are not open to changing that. |
Hi @LinuxMagicSupportTeam I've created export templates to extract the data in a format that I can import back in again to Netbox. Here's the one I use for interfaces. Just create a new template and add a CSV extension. Select DCIM | Interface as the assigned module and then add the below Jinja2 code.
|
Please see the FAQ on our wiki. Please also remember to search for issues before creating a new one. |
Deployment Type
Self-hosted
NetBox Version
v3.7.6
Python Version
3.10
Steps to Reproduce
Devices / Device Components / Interfaces / Export|Import:
(the purpose is to "clone" the interfaces for the new device, which is a clone of the another device)
Issue 1: the exported CSV's headers have upper case letters which the Import process can't recognize.
Issue 2: all the "type" values seem to be invalid choices, despite the data being specified by the Export process
sample CSV data:
e.g. Error shown:
Expected Behavior
The Exported CSV should be importable by the Import process without the header and type issues.
Observed Behavior
CSV headers in upper case not recognized
"type" data all seem to be invalid
The text was updated successfully, but these errors were encountered: