Parent Form Data Store

Introduction

The Parent Form Data Store is intended to be used in a subform where the subform data will be saved using the parent form's data store instead of its own. This feature ensures that the data contained within the subform is passed to the immediate parent’s data store for saving rather than just using the parent data store's table name.

How it differs from the default Data Store

• Default behavior: Each subform saves its data into its own dedicated database table.
• With Parent Form Data Store: The subform’s fields are written as columns in the parent form’s table, alongside the parent’s own fields. No separate table is created.

When to use Parent Form Data Store

Choose this option when your subform is simply a visual grouping of fields within the parent form, not a repeating set of child records.
Example: A parent form for "Employee" might have a subform grouping fields like "Emergency Contact Name" and "Emergency Contact Phone." These belong in the employee’s record, not in a separate table.

When not to use Parent Form Data Store

Avoid using Parent Form Data Store if your subform represents a repeating collection of related records.
Example: An "Employee" form with a subform for "Previous Jobs" should use its own data store, since each employee can have multiple job records.