Standardize on mechanism for specifying generic related objects during CSV import #4242

Closed
opened 2025-12-29 18:34:12 +01:00 by adam · 0 comments
Owner

Originally created by @jeremystretch on GitHub (Nov 3, 2020).

Originally assigned to: @jeremystretch on GitHub.

Proposed Changes

When importing objects in CSV format, require specifying the related object type in the form <app>.<model> for consistency. The following forms need to be updated:

  • CableCSVForm: Import A/B terminations using model name only
  • IPAddressCSVForm: assigned_object_type does not use CSVModelChoiceField
  • SecretCSVForm: Object type uses model name only

Justification

Ensures a consistent UX for importing all types of objects.

Originally created by @jeremystretch on GitHub (Nov 3, 2020). Originally assigned to: @jeremystretch on GitHub. ### Proposed Changes When importing objects in CSV format, require specifying the related object type in the form `<app>.<model>` for consistency. The following forms need to be updated: * CableCSVForm: Import A/B terminations using model name only * IPAddressCSVForm: `assigned_object_type` does not use CSVModelChoiceField * SecretCSVForm: Object type uses model name only ### Justification Ensures a consistent UX for importing all types of objects.
adam added the status: acceptedtype: housekeeping labels 2025-12-29 18:34:12 +01:00
adam closed this issue 2025-12-29 18:34:12 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4242