CSV import should accept the "slug" value for choice fields #5003
Labels
status: accepted
This issue has been accepted for implementation
type: feature
Introduction of new functionality to the application
Milestone
Environment
Proposed Functionality
For fields which specify one of several pre-defined choices, users should be able to specify the "slug" value rather than the proper string. For example, here are the available slug values and corresponding names for a rack's type:
2-post-frame
4-post-frame
4-post-cabinet
wall-frame
wall-cabinet
It may make sense to use the slug value consistently for both import and export operations, though I'll leave that open for discussion.
Use Case
NetBox v2.7 replaced the old integer-based choice field IDs with human-friendly slugs. These are more convenient to handle when manipulating data, as extra attention is not needed to ensure correct capitalization, spacing, or punctuation. For example, it is quicker and simpler to write
wall-frame
thanWall-mounted frame
, and the later provides no further information than the former within the context of data entry.Database Changes
None
External Dependencies
None
The text was updated successfully, but these errors were encountered: