Fixing Form Validation for Related Models in Django

You've correctly identified the issue. The validation errors occur because your related forms (ContactForm, HiringForm, etc.) include the employee field in their validation, but the Employee object doesn't exist yet when validation happens.

The Problem

When you use fields = '__all__' in your ModelForms, Django includes all fields from the model, including foreign key fields like employee. Since the Employee instance doesn't exist during initial validation, these fields fail validation with "This field is required" errors.

Solution: Exclude the Employee Field

The best approach is to exclude the employee field from each related form and set it programmatically after saving the Employee instance:

PYTHONCopied
class ContactForm(forms.ModelForm):
    class Meta:
        model = Contact
        exclude = ['employee']

class HiringForm(forms.ModelForm):
    class Meta:
        model = Hiring
        exclude = ['employee']
        widgets = {
            'data_admissao': forms.DateInput(attrs={'type': 'date'}),
            'hora_entrada': forms.TimeInput(attrs={'type': 'time'}),
            'hora_saida': forms.TimeInput(attrs={'type': 'time'}),
        }

# Apply the same pattern to all other related forms
class PaymentForm(forms.ModelForm):
    class Meta:
        model = Payment
        exclude = ['employee']

class SystemUserForm(forms.ModelForm):
    class Meta:
        model = SystemUser
        exclude = ['employee']

class DocumentsForm(forms.ModelForm):
    class Meta:
        model = Documents
        exclude = ['employee']

class ChildrenForm(forms.ModelForm):
    class Meta:
        model = Children
        exclude = ['employee']
        widgets = {
            'filho_nascimento': forms.DateInput(attrs={'type': 'date'}),
        }

Improved View Logic

You should also restructure your view to validate all forms before saving any of them:

PYTHONCopied
def employee_record(request):
    if request.method == 'POST':
        employee_form = EmployeeForm(request.POST)
        contact_form = ContactForm(request.POST)
        hiring_form = HiringForm(request.POST)
        payment_form = PaymentForm(request.POST)  # Fixed typo in PaymentForm
        system_user_form = SystemUserForm(request.POST)
        documents_form = DocumentsForm(request.POST)
        children_form = ChildrenForm(request.POST)

        # Check if all forms are valid before saving any
        if (employee_form.is_valid() and 
            contact_form.is_valid() and 
            hiring_form.is_valid() and 
            payment_form.is_valid() and  # Fixed typo
            system_user_form.is_valid() and 
            documents_form.is_valid() and 
            children_form.is_valid()):
            
            # Save the employee first
            employee = employee_form.save()
            
            # Then save all related forms with the employee reference
            contact = contact_form.save(commit=False)
            contact.employee = employee
            contact.save()
            
            hiring = hiring_form.save(commit=False)
            hiring.employee = employee
            hiring.save()
            
            payment = payment_form.save(commit=False)
            payment.employee = employee
            payment.save()
            
            system_user = system_user_form.save(commit=False)
            system_user.employee = employee
            system_user.save()
            
            documents = documents_form.save(commit=False)
            documents.employee = employee
            documents.save()
            
            children = children_form.save(commit=False)
            children.employee = employee
            children.save()
            
            return redirect('index')
    
    # Your code for GET request handling...

Additional Notes

1. I fixed a typo in your view: PaymnentForm should be PaymentForm
2. You had payment_form_form in your validation check, which should be payment_form
3. Consider using Django's form prefixes if you have multiple forms with potentially overlapping field names
4. For the Children model, if it's a one-to-many relationship (an employee can have multiple children), you might want to use formsets instead

This approach ensures all forms are validated before any data is saved, and the employee reference is properly set for all related models.