Steps to Fill in the OrgStructure Table (Complete Guide)

This table is essential in mapping survey responses to the correct organizational unit, maintaining organizational hierarchy, and controlling data flow across modules.

✅Note: The osname and oscode should always be identical to the graph optionBold Text name to avoid discrepancies.

For a complete description of the table structure and field explanations, please refer to the → OrgStructure Table Structure

This is the primary key (auto-incremented) for the table.
Do not manually enter this value if inserting data directly via the database.
It is automatically generated.

The masterosid acts as a foreign key, linking the current organizational unit to its master structure defined in the orgstructuremaster table.

Example: If you have a Cluster Midden in the master structure, its masterosid will point to the corresponding master entry.

Example: masterosid = 1 → Refers to “Cluster Midden” in orgstructuremaster.

The osname represents the full name of the organizational unit.

1. This name should exactly match the graph option name to maintain consistency.
2. It is displayed in survey reports and dashboards.

Example: osname = “Cluster Midden” osname = “Stilleweer (in Appingedam)”

The oscode serves as an internal code representing the organizational structure.

1. It is often the same as osname but can be customized.
2. This code is crucial in database queries and report filters.

Example: oscode = “Cluster Midden” oscode = “Stilleweer (in Appingedam)”

This column defines the parent-child relationship within the organizational hierarchy.

1. If the organizational unit is top-level, set parentosid = 0.
2. If the unit is under another structure, enter the id of the parent.

Example:

1. For Cluster Midden → parentosid = 0
2. For Stilleweer (in Appingedam) → parentosid = 1 (refers to Cluster Midden)

This column identifies the branch associated with the organizational unit.

1. It usually links to the branches table.
2. You can use comma-separated branch IDs if multiple branches are associated.

Example: branchid = 1 → Linked to Branch ID 1
branchid = 1,2 → Linked to Branch ID 1 and 2

This field captures the module(s) associated with the organizational unit.

1. The value should correspond to the module IDs from the modulesettingoptions table.
2. Separate multiple module IDs with commas.

Example:

1. moduleids = 1 → Linked to Module ID 1
2. moduleids = 1,2 → Linked to Module ID 1 and 2

The osorder column defines the order in which organizational units appear.

Lower numbers appear first, higher numbers appear later. This affects the display order in reports and dashboards.

Example:

1. osorder = 1 → Appears first
2. osorder = 5 → Appears fifth

This column controls whether the organizational unit is active or inactive.

1. Active units appear in survey selection and reports.
2. Inactive units are hidden but preserved in the database.

This column captures the user ID of the person who created the organizational unit.

1. It is automatically populated by the system.
2. Do not modify this value manually.

This field stores the timestamp when the record was created.

1. It is automatically generated.
2. Avoid modifying this field unless required.

This column captures the user ID of the person who last modified the record.

1. This field is automatically populated.
2. Avoid manual changes.

This field captures the timestamp of the last modification.

1. It is automatically updated.
2. Avoid modifying this field manually.

1. Always ensure that osname and oscode match the graph option name.
2. Maintain correct parentosid for hierarchical reporting.
3. Keep inactive units preserved to avoid data loss.

Here’s an example of a complete record for a single organizational structure:

This guide ensures accurate data entry for organizational units, enabling precise reporting and hierarchical data structuring.