Form validation (is_valid, cleaned_data) in Django - Step-by-Step Execution

Concept Flow - Form validation (is_valid, cleaned_data)

Create Form Instance with Data

↓

Call is_valid()

↓

Access cleaned_data

↓

Use Valid Data

The form is created with data, then is_valid() checks if data is good. If yes, cleaned_data holds cleaned inputs; if no, errors show.

Execution Sample

Django

form = MyForm(data=request.POST)
if form.is_valid():
    name = form.cleaned_data['name']
else:
    errors = form.errors

This code creates a form with POST data, checks if it's valid, then uses cleaned data or errors accordingly.

Execution Table

Step	Action	is_valid() Result	cleaned_data Content	errors Content
1	Create form with POST data	Not called yet	Empty	Empty
2	Call form.is_valid()	True	{'name': 'Alice'}	Empty
3	Access form.cleaned_data['name']	True	'Alice'	Empty
4	No errors since valid	True	{'name': 'Alice'}	Empty
5	End of valid flow	True	{'name': 'Alice'}	Empty
6	Create form with bad POST data	Not called yet	Empty	Empty
7	Call form.is_valid()	False	Empty	{'name': ['This field is required.']}
8	Try to access cleaned_data	False	Empty	{'name': ['This field is required.']}
9	Access form.errors	False	Empty	{'name': ['This field is required.']}
10	End of invalid flow	False	Empty	{'name': ['This field is required.']}

💡 Execution stops after form.is_valid() returns True or False, determining next steps.

Variable Tracker

Variable	Start	After Step 2	After Step 7	Final
form	Empty form instance	Form with valid data	Form with invalid data	Form instance
is_valid()	Not called	True	False	Boolean result
cleaned_data	Empty	{'name': 'Alice'}	Empty	Depends on validity
errors	Empty	Empty	{'name': ['This field is required.']}	Depends on validity

Key Moments - 3 Insights

Why can't I access cleaned_data if is_valid() returns False?

cleaned_data only fills when is_valid() is True, as shown in execution_table rows 2 and 7. If invalid, cleaned_data stays empty.

What does is_valid() actually do?

is_valid() runs all field checks and validations. It returns True if all data is good (row 2), else False (row 7), controlling flow.

Why do errors appear only after is_valid()?

Errors are collected during validation inside is_valid(). Before calling it, errors are empty (row 1), after invalid check errors fill (row 7).

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what is the value of form.cleaned_data['name']?

A Empty

B None

C 'Alice'

D Error

💡 Hint

Check the cleaned_data Content column at step 3 in execution_table.

At which step does is_valid() return False?

A Step 7

B Step 2

C Step 3

D Step 9

💡 Hint

Look at the is_valid() Result column in execution_table for step 7.

If the form data is missing required fields, what will form.errors contain after is_valid()?

A Empty dictionary

B Error messages for missing fields

C Cleaned data values

D Boolean True

💡 Hint

See errors Content column in execution_table at step 7 and 9.

Concept Snapshot

Django form validation:
- Create form with data: form = MyForm(data)
- Call form.is_valid() to check data
- If True, use form.cleaned_data for safe inputs
- If False, use form.errors to show problems
- cleaned_data only available after valid check

Full Transcript

In Django, form validation starts by creating a form instance with user data. Calling is_valid() runs checks on the data. If all fields pass, is_valid() returns True and cleaned_data holds the cleaned inputs. If any field fails, is_valid() returns False and errors contain messages explaining what is wrong. You should only use cleaned_data after is_valid() returns True. This process helps safely handle user input and show helpful error messages.

Practice

1. What does the is_valid() method do in a Django form?

easy

A. Saves the form data to the database

B. Clears all data from the form fields

C. Checks if the form data meets all validation rules

D. Generates HTML for the form

Solution

1. Step 1: Understand the purpose of is_valid()

   This method runs all validation checks on the form data to ensure it is correct and complete.

2. Step 2: Identify what is_valid() returns

   It returns True if all data passes validation, otherwise False.

3. Final Answer:

   Checks if the form data meets all validation rules -> Option C

4. Quick Check:

   Form validation = is_valid() [OK]

Hint: Remember: is_valid() means data is good to use [OK]

Common Mistakes:

• Thinking is_valid() saves data
• Confusing is_valid() with form rendering
• Assuming is_valid() clears form fields

2. Which of the following is the correct way to access cleaned form data after validation?

easy

A. form.get_cleaned('field_name')

B. form.data['field_name']

C. form.fields['field_name']

D. form.cleaned_data['field_name']

Solution

1. Step 1: Identify how cleaned data is stored

   After calling is_valid(), valid data is stored in cleaned_data dictionary.

2. Step 2: Access cleaned data by field name

   You use form.cleaned_data['field_name'] to get the safe, validated value.

3. Final Answer:

   form.cleaned_data['field_name'] -> Option D

4. Quick Check:

   Access safe data = cleaned_data['field_name'] [OK]

Hint: Use cleaned_data after is_valid() to get safe inputs [OK]

Common Mistakes:

• Using form.data which is raw input, not validated
• Trying to call a non-existent method get_cleaned()
• Accessing form.fields which holds field definitions, not data

3. Given this code snippet:

form = MyForm(request.POST)
if form.is_valid():
    name = form.cleaned_data['name']
else:
    errors = form.errors

What will errors contain if the form is invalid?

medium

A. A dictionary of error messages for each invalid field

B. An empty list

C. The cleaned data from the form

D. A boolean False value

Solution

1. Step 1: Understand what form.errors holds

   When validation fails, form.errors contains error messages keyed by field names.

2. Step 2: Differentiate errors from cleaned_data

   Errors are messages explaining what went wrong, not data or booleans.

3. Final Answer:

   A dictionary of error messages for each invalid field -> Option A

4. Quick Check:

   Invalid form errors = form.errors dict [OK]

Hint: form.errors holds messages, not data or booleans [OK]

Common Mistakes:

• Confusing errors with cleaned_data
• Expecting errors to be a list or boolean
• Assuming errors is empty when invalid

4. What is wrong with this code?

form = MyForm(request.POST)
if form.is_valid:
    data = form.cleaned_data

medium

A. request.POST should be request.GET

B. Missing parentheses after is_valid, so validation is not called

C. cleaned_data should be called as a method

D. form variable is not defined

Solution

1. Step 1: Check how is_valid is used

   The code uses form.is_valid without parentheses, so it references the method but does not call it.

2. Step 2: Understand the effect of missing parentheses

   Without calling is_valid(), validation does not run and cleaned_data is not populated.

3. Final Answer:

   Missing parentheses after is_valid, so validation is not called -> Option B

4. Quick Check:

   Call is_valid() with () to validate [OK]

Hint: Always add () to call is_valid method [OK]

Common Mistakes:

• Forgetting parentheses on is_valid()
• Trying to call cleaned_data as a method
• Confusing POST and GET without context

5. You want to create a form that only accepts an email if the user is over 18 years old. Which approach correctly uses is_valid() and cleaned_data to enforce this?

hard

A. Call is_valid(), then check cleaned_data['age'] to conditionally accept the email

B. Check form.data['age'] before calling is_valid()

C. Use form.errors before calling is_valid()

D. Assign cleaned_data before calling is_valid()

Solution

1. Step 1: Understand validation order

   You must call is_valid() first to run all validations and populate cleaned_data.

2. Step 2: Use cleaned_data to check age and decide if email is accepted

   After validation, cleaned_data['age'] is safe to use for conditional logic.

3. Final Answer:

   Call is_valid(), then check cleaned_data['age'] to conditionally accept the email -> Option A

4. Quick Check:

   Validate first, then use cleaned_data [OK]

Hint: Always validate before using cleaned_data for conditions [OK]

Common Mistakes:

• Using raw data before validation
• Accessing errors before validation
• Trying to use cleaned_data before calling is_valid()