🐉 Boss fight · 150 XP

Boss: model a course platform's schema

🐉 Boss: model a course platform

You're building the schema for a tiny course platform (sound familiar?). Students are Contacts, and they enroll in Courses.

Requirements

1. A custom object Course__c (record name: text)
2. A junction object Enrollment__c (record name: auto-number like E-{0000})
3. On Enrollment__c, two master-detail fields:
   • Course__c → Course
   • Contact__c → Contact
4. On Course__c, a roll-up summary field Student_Count__c that COUNTs its Enrollments

Hints

• Create the master-detail to Course__c first, so it becomes the primary master
• Roll-up summary fields only appear as an option on the master side, and only once the master-detail exists
• API names matter. Quill checks them exactly

When you hit Submit, Quill creates a course, a student and an enrollment, then checks that your roll-up counts 1. Everything gets rolled back afterwards.

🦝 Three objects, two relationships, one roll-up. Quill believes in you. Mostly.