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

Custom Fields omitted from Import "Field Options" Table if UI Visibility set to 'Hidden (if unset)' #8434

New Issue
Closed
opened 2025-12-29 20:36:39 +01:00 by adam · 0 comments
adam commented 2025-12-29 20:36:39 +01:00
Owner
Copy Link

Originally created by @ross-cello on GitHub (Aug 8, 2023).

Originally assigned to: @kkthxbye-code on GitHub.

NetBox version

v3.5.7

Python version

3.9

Steps to Reproduce

  1. Take any Custom Field object and change the UI Visibility to 'Hidden (if unset)
  2. Go to a mass import page, eg https://{netbox-host}/circuits/circuits/import/
  3. Observe the lack of presence for said Custom Field object in the Field Options table

Expected Behavior

Expect the Custom Fields to be present in the Field Options table to aid in crafting CSV's with required formatting.

Observed Behavior

CF options are omitted from the Field Objects table, and so you generally need to gather requisite information in a roundabout manner.
Export creates fields as Label Value, so you generally still need to parse CF's for the right Import formatting; can be a nuisance.

We like the newer capability of hiding unused fields from UI, but we have less skilled users using Netbox and so hope an exception can be made here for restoration of CF visibility in Import scenarios.

Originally created by @ross-cello on GitHub (Aug 8, 2023). Originally assigned to: @kkthxbye-code on GitHub. ### NetBox version v3.5.7 ### Python version 3.9 ### Steps to Reproduce 1. Take any Custom Field object and change the UI Visibility to 'Hidden (if unset) 2. Go to a mass import page, eg https://{netbox-host}/circuits/circuits/import/ 3. Observe the lack of presence for said Custom Field object in the Field Options table ### Expected Behavior Expect the Custom Fields to be present in the Field Options table to aid in crafting CSV's with required formatting. ### Observed Behavior CF options are omitted from the Field Objects table, and so you generally need to gather requisite information in a roundabout manner. Export creates fields as Label Value, so you generally still need to parse CF's for the right Import formatting; can be a nuisance. We like the newer capability of hiding unused fields from UI, but we have less skilled users using Netbox and so hope an exception can be made here for restoration of CF visibility in Import scenarios.
adam added the type: bugstatus: accepted labels 2025-12-29 20:36:39 +01:00
adam closed this issue 2025-12-29 20:36:40 +01:00
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 status: accepted type: bug
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#8434
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?