remove-model-field

Removing a NetBox model field requires updating tests, documentation, GraphQL, API serializers, forms, filtersets, tables, and search indexing first. This prevents runtime FieldErrors and import failures by ensuring no broken references remain before deleting the model field itself.

When deleting a NetBox model field, clean the GraphQL filter and type declarations in filters.py and types.py. You must also remove both the FK and FK_id companions from FilterSets to prevent GraphQL schema errors.

No, you should generate the Django migration using makemigrations rather than manual edits. After removing the NetBox model field, verify the generated migration file contains only the intended RemoveField operation before applying it.

Import failures occur because foreign key fields are referenced across multiple NetBox components including filtersets, tables, and search indexing. Removing a field without cleaning its FK and FK_id companions leaves broken references that trigger Django runtime FieldErrors.

You must update API serializer Meta.fields, filtersets, forms, tables, UI panels, search indexing, tests, and documentation. Verifying that database constraints, indexes, and orderings no longer reference the field is also required to prevent runtime FieldErrors.