UDISE Plus Student Registration 2026-27 – 5 Form Errors That Stop Data Entry

UDISE Plus Student Registration SDMS GP EP SF Data Entry Problems 2026-27
UDISE Plus Student Registration SDMS GP EP SF Data Entry Problems 2026-27
🏛
Official UDISE+ Portal: This guide is based on the official UDISE+ Portal — udiseplus.gov.in. For login, data entry, and all official UDISE+ services, always go directly to the official portal.

Where Student Registration Form Actually Fails

The student registration form in SDMS has three sections: GP (General Profile), EP (Enrollment Profile), and SF (Student Facilities). Each section has a Save button. The form looks simple. It is not simple once you are 20 students in.

By student 10, the Save button in GP stops responding for one student and you cannot tell why. By student 15, EP shows a "duplicate admission number" error. By student 22, APAAR ID generates on screen but the confirmation message never appears. By student 30, you are not sure which students actually saved and which did not.

These are form-level failures — they happen within the registration process itself, for specific reasons in specific fields. This page covers the 5 points where student registration breaks down and exactly what to fix at each one.

🔍
Form errors covered in this guide:
  • GP save fails with no error message — which mandatory fields cause it
  • EP duplicate admission number and roll number conflicts
  • SF validation failures — which SF fields block submission
  • APAAR generates on screen but does not persist after save
  • Student exists in wrong year or wrong school — search pulls wrong record

Problem 1: GP Save Fails Silently — The Hidden Mandatory Field

You filled the student's name, date of birth, gender, category, parents' names, and address. You clicked Save. Nothing happened — no error, no success message. The page just reloaded.

Operators commonly miss these silent mandatory fields in GP:

  • Social Category — the dropdown must not be on "Select." You must choose a value: SC, ST, OBC, or General. If you do not know the correct category, use General temporarily and update it once you obtain the caste certificate.
  • Religion — most state portals require this. Leaving it on "Select" causes silent save failure.
  • Mother's Name — some state portals treat this as mandatory even though it appears optional visually. If you do not know the mother's name, enter "Not Available" — do not leave it blank.
  • Aadhaar Number format — must be exactly 12 digits. A 13-digit entry (extra space or digit) causes save failure without an obvious error message.
  • State/District/Block in address — these are dropdown fields. If you leave these fields at the first empty option, the save fails.

Fix: Before clicking Save, scroll through every visible field top to bottom. Any field still showing "Select..." or a blank input is the cause of the failure. Most portals do not highlight these fields in red until after you try to save — check before clicking, not after.

💡
Save GP separately. After filling GP, click Save and wait for the success confirmation before moving to EP. If save fails, fix only GP before touching EP.

Problem 2: EP Conflicts — Duplicate Numbers and Wrong Enrollment Type

The Enrollment Profile section has three fields that must be unique: Admission Number, Roll Number, and — in some state portals — Section + Roll Number combination. If any of these duplicates an existing student in the same class, the EP save fails.

Common EP errors:

  • Duplicate Admission Number: Each student must have a unique admission number across the entire school — not just within a class. If a student left years ago and the school never re-issued their admission number, you cannot assign it to a new student. Check your admission register for numbers that operators are currently using.
  • Duplicate Roll Number: You must assign unique roll numbers within the same class and section. In schools with small class sizes, operators sometimes use 1, 2, 3 for every class — Class 3 has Roll 1 and Class 4 also has Roll 1. This is allowed only if they are different classes. Same class, same roll number is always an error.
  • Wrong Enrollment Type: Operators must assign the enrollment type "Promoted" to promoted students. You must assign "New Admission" to new Class 1 students. You must assign "Transfer In" to students coming from another school. Using "New Admission" for a promoted student creates wrong academic history in APAAR records.

Problem 3: SF Validation — Small Checkboxes, Big Consequences

The Student Facilities section looks simple — mostly Yes/No fields. But SF has two specific failure points:

  1. Mid-Day Meal field left on "Select": Many portals require you to actively choose Yes or No for mid-day meal. If you leave the Mid-Day Meal field on 'Select', the SF save fails. Even if the student does not receive mid-day meal, select "No" explicitly.
  2. RTE Admission field not filled for Class 1 students: For students who gained admission under the Right to Education Act (25% EWS quota), the RTE Admission field must be "Yes." For students who did not gain admission under RTE, select "No." If you skip this field for new Class 1 admissions, the SF validation will fail.

SF data directly connects to government grant calculations — schools that enter "No" for mid-day meal when students do receive it will show a lower mid-day meal count in the Report Module, which affects food allocation for the school.

Problem 4: APAAR Generates But Does Not Save

Authentication succeeded. The portal showed a 12-digit APAAR ID on screen. You closed the student's profile. When you reopened it — the APAAR field is blank.

This happens in two specific situations:

  • If the OTP process takes longer than expected, the session may expire. The APAAR appears on screen but the portal rejects the save request because the session is invalid. Fix: log out, log back in, find the student, and repeat the APAAR generation process.

Problem 5: Student Already Exists — Wrong Year or Wrong School

You click "Add New Student" and enter the Aadhaar number. The portal shows a student profile — but it is from 2025-26, or it is linked to a different school.

What You SeeWhat It MeansWhat to Do
Student appears with your school, wrong yearLast year's profile exists but the operator did not apply the promotionUse Promote function — do not create a new entry
Student appears with a different schoolOld school did not mark them as Transfer OutUse "Link to My School" or "Transfer In" — contact BRC if blocked
Student appears with correct school and yearThe operator started data entry earlier and saved it as a draftOpen the existing draft and complete it — do not create a duplicate
Student appears with wrong name or DOBAnother school created a record with same Aadhaar due to errorReport to Block MIS Coordinator — do not overwrite

Correct Registration Sequence — Do This Order Every Time

  1. Collect all Aadhaar cards for the students you will enter today — physical cards or Aadhaar prints
  2. For each student, enter Aadhaar number first in the Add Student search — check if a record already exists
  3. If new: fill GP — name exactly as on Aadhaar, DOB exactly as on Aadhaar, tick consent checkbox
  4. Authenticate Aadhaar and generate APAAR ID — wait for the success/saved confirmation
  5. Click Save on GP — wait for confirmation before moving to EP
  6. Fill EP — admission number (unique across school), roll number (unique within class), correct enrollment type
  7. Click Save on EP — wait for confirmation
  8. Fill SF — all fields must have Yes or No, no fields left on Select
  9. Click Save on SF
  10. Move to next student — do not open multiple student profiles in parallel tabs
One student at a time, save after each section. Opening multiple student profiles in parallel browser tabs causes session conflicts, and a save from one tab can overwrite another. The developers designed SDMS for sequential entry.

❓ Frequently Asked Questions (FAQs)

Here are the most common questions people ask about UDISE Plus Student Registration 2026-27 – 5 Form Errors That Stop Data Entry.

Fill GP first and save. Then fill EP and save. Then fill SF and save. Do not fill all three and save once at the end. If the final save fails, you cannot tell which section caused the failure. Saving after each section means if a failure happens, you know exactly which section needs fixing — and you have not lost the other two sections' data.
A duplicate roll number will either block the save with an error message (in most state portals) or save without warning but cause a data conflict at BRC certification. If you get a duplicate roll error, edit the EP of one student and assign a unique roll number. If your class does not have a formal roll number sequence, use the admission register number as the roll number — that ensures uniqueness since admission numbers remain unique per school.
Yes, in most state SDMS portals you can save a GP with a blank Aadhaar — but the record remains incomplete and you cannot generate the APAAR ID. The save succeeds at the draft level, but the system cannot certify the student without the APAAR. You will be able to submit the module but BRC will reject it because of missing APAAR IDs. Always fill Aadhaar and generate APAAR before considering a student's record complete.
Add them as a new entry, not a promotion. Go to "Add Student" and search by their Aadhaar number first. If the previous school entered them in SDMS, their profile will appear. Click "Link to My School" or "Transfer In." Their APAAR ID and previous academic history carry over. In EP, select enrollment type as "Transfer In" — not "New Admission" and not "Promoted." Using the wrong enrollment type causes their academic record to show incorrect history.
You can save GP and EP and leave SF incomplete temporarily. However, you must complete the SF section before you can submit the module. Many operators make the mistake of finishing all students' GP and EP across 2-3 days, then sitting down to fill SF — and finding that session history is difficult to track. Best practice: finish all three sections for each student before moving to the next.
Open the student's profile, go to Enrollment Profile (EP), and update their status to "Transfer Out" with the date. Once you update the transfer status, go to SF and change Mid-Day Meal to "No" and add the last date of meal receipt. The SF data should reflect their actual situation as of September 30 — if the student had already transferred before that date, the SF section must show no active facilities.

✅ Conclusion

The GP → EP → SF sequence is simple in theory, but each section has specific fields that cause silent failures. The single biggest time-waster in student registration is filling all three sections and then discovering the save failed — with no clear error message. The fix is to save after each section individually, check for the specific mandatory fields listed here before clicking Save, and verify that you include the consent checkbox when generating the APAAR ID before closing a student's profile. Schools that fill 10 students and save once at the end lose more time than schools that save after every student.

Pooja Sharma
Written By

Pooja Sharma

Teacher & Contributor 🎓 BSc. (Physics), MSc. (Physics) and BEd.

Pooja Sharma is a qualified physics graduate (BSc, MSc) and certified teacher (BEd). As an active educator and contributor, she simplifies complex school portal processes, student registrations, and educational data entry tasks for academic administrators.

🗺️ Direct SDMS Login – Quick Access by State

Click your state below for the direct UDISE Plus SDMS login link and complete data entry guide.

All 39 States & UTs →