When working with self-referential models in Django, a common error occurs when assigning data to the ForeignKey field. The error message indicates that a QuerySet or string was incorrectly passed where an actual model instance was expected.

The Problem

Consider this Area model representing a hierarchical region structure (countries, provinces, cities):

from django.db import models


class Area(models.Model):
    """
    Self-referential model for administrative regions.
    Provinces, cities, and counties exist in a single table.
    Provinces have parent=None, cities have parent=province, counties have parent=city.
    """
    name = models.CharField(max_length=32, verbose_name='Region Name')
    parent = models.ForeignKey('self', verbose_name='Parent Region', on_delete=models.CASCADE, null=True)

    def __str__(self):
        return self.name

    class Meta:
        db_table = 'regions'
        verbose_name = 'Region'
        verbose_name_plural = verbose_name

When attempting to create a new record, the following operations all fail or succeed differently:

# This fails - passing a string directly
Area.objects.create(name='Peking', parent='China')
# ValueError: Cannot assign "'China'": "Area.parent" must be a "Area" instance.

# This also fails - assigning a QuerySet
Area.objects.create(name='Peking', parent=Area.objects.filter(name='China'))
# ValueError: Cannot assign "<QuerySet [<Area: China>]>": "Area.parent" must be a "Area" instance.

# This works - passing the actual model instance
parent_region = Area.objects.filter(name='China').first()
Area.objects.create(name='Peking', parent=parent_region)
# <Area: Peking>

Root Cause

Django's ForeignKey field requires an actual model instance, not a QuerySet or raw string value. When you filter for an object with Area.objects.filter(name='China'), you receive a QuerySet containing potential matches, not the instance itself. Similarly, passing the string 'China' bypasses Django's relationship resolution entirely.

Solution

Extract the model instance from the QuerySet using one of these approaches:

# Method 1: Using first() returns the instance or None
province = Area.objects.filter(name='Guangdong').first()
if province:
    Area.objects.create(name='Shenzhen', parent=province)

# Method 2: Using get() returns the instance directly (raises DoesNotExist if not found)
try:
    country = Area.objects.get(name='China')
    Area.objects.create(name='Shanghai', parent=country)
except Area.DoesNotExist:
    pass

# Method 3: Chaining with first() inline
Area.objects.create(
    name='Guangzhou',
    parent=Area.objects.filter(name='Guangdong').first()
)

Key Takeaway

When assigning a ForeignKey relationship in Django, always ensure you're passing an actual model instance retrieved via .get() or .first() (not .filter() directly). The QuerySet returned by .filter() represents a collection of potential matches, not a single object suitable for foreign key assignment.