Now, to let a subform act as an independent form within the record, we are introducing the 'Mark as required' feature to subforms.

Marking subform as required

For example, if you want to collect the professional experience of an applicant before onboarding them to an executive course, you can mark the subform as required, collect the details, and save the record to process it further.

It is important to note, if you attempt to save a row without data in mandatory fields, inside a mandatory subform, then the record will not be saved until the mandatory fields are filled.

• If a subform is not marked as required, you can save the record with or without a subform value.
  
• If you have not marked a subform as required, but there are fields within the subform that are marked mandatory, you can still save the record without any values filled in them.
  For example, to enroll for a diploma course, professional experience may not be required. In that case, you can skip from filling a row in the subform.
  
  However, if you have data at hand to fill the subform, then filling any row will require all the mandatory fields also to be filled.
  Let us consider this example where iPhone 13 is a product record and the accessories are maintained as a subform. If you have an accessory to add to the iPhone record, then the mandatory field - product compatibility should be filled in. Any attempt to save the record without populating that field will not be successful.