CreateModes

In Simple mode, the generated table will contain a column for each immediate child Data Field of the selected Data Field Container.
No fields from ancestor or descendant containers are included.

• Use this mode when you want a table that directly reflects the structure of a single Data Table, Data Section, or Data Model.
• Relationships to other containers are not represented.
• The resulting table is straightforward and easy to use for simple export or reporting scenarios.

Example:
If the selected scope is a Data Table with fields "Item", "Quantity", and "Price", the resulting table will have columns for each of these fields only.

In Flatten mode, the generated table will include columns for all single-instance fields found in the selected Data Field Container and all of its ancestor containers, up to the root Data Model. This produces a denormalized, wide table that combines fields from multiple levels of the data model hierarchy.

• Use this mode when you need to export or report on data that spans multiple containers, but do not require normalized relationships.
• Useful for scenarios where a single row should contain all relevant data for a record, regardless of its original hierarchy.
• Only single-instance fields are included; repeating or collection fields are not flattened.

Example:
If the selected scope is a Data Table inside a Data Section with a "SectionName" field, the resulting table will include columns for "SectionName" and all fields from the Data Table.

In Recursive mode, a normalized set of tables is generated for the selected Data Field Container and all of its descendant containers.
Each table includes an 'Id' column as a primary key, and foreign key columns are added to represent parent-child relationships between containers.

• Use this mode to mirror the full hierarchy of your data model in the database, preserving relationships between containers.
• Enables advanced reporting, integration, and data integrity scenarios where normalized relational structure is required.
• Each container (such as a Data Table, Data Section, or Data Model) becomes its own table, with appropriate keys and references.

Example:
If the selected scope is a Data Model with nested Data Sections and Data Tables, each container will become a separate table, and foreign keys will link child tables to their parents.