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

Export fields do not always match import fields. #3521

New Issue
Closed
opened 2025-12-29 18:29:37 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:29:37 +01:00
Owner
Copy Link

Originally created by @ryanmerolle on GitHub (Mar 30, 2020).

Environment

  • Python version: 3.6.9
  • NetBox version: 2.7.11

Steps to Reproduce

  1. Export any sort of data type.
  2. Delete associated data.
  3. Import same csv/data into netbox
  4. Import fails for a number of fields:
  • Any custom field is exported as the custom field's name like field1, but the import requires cf_field1
  • Units such as outer_unit (racks) export outputs in instead of the expected Inches
  • I will go throug some other exports to document what else does not match.

Expected Behavior

Any export would be able to work as an import assuming the linked records are present(manufacture for example with device type).

Observed Behavior

  • Field names do not match export and import (at least for custom fields missing the cf_ prefix).
  • Exported field values do not match allowed schema/constraints for the data model / import.
Originally created by @ryanmerolle on GitHub (Mar 30, 2020). ### Environment * Python version: 3.6.9 * NetBox version: 2.7.11 ### Steps to Reproduce 1. Export any sort of data type. 2. Delete associated data. 3. Import same csv/data into netbox 4. Import fails for a number of fields: - Any custom field is exported as the custom field's name like `field1`, but the import requires `cf_field1` - Units such as outer_unit (racks) export outputs `in` instead of the expected `Inches` - I will go throug some other exports to document what else does not match. ### Expected Behavior Any export would be able to work as an import assuming the linked records are present(manufacture for example with device type). ### Observed Behavior - Field names do not match export and import (at least for custom fields missing the `cf_` prefix). - Exported field values do not match allowed schema/constraints for the data model / import.
adam closed this issue 2025-12-29 18:29:38 +01:00
adam commented 2025-12-29 18:29:38 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 30, 2020):

They're not always going to match, for various reasons. This was never a design goal.

@jeremystretch commented on GitHub (Mar 30, 2020): They're not always going to match, for various reasons. This was never a design goal.
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#3521
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?