Steps to Fill in the OrgStructureMaster Table (Complete Guide)

This guide provides a step-by-step approach to correctly fill the OrgStructureMaster table. This table stores information about the hierarchical organizational structure for a given client. It helps define different levels within an organization, and specifies whether a particular level is used for evaluation purposes.

The table is critical for structuring survey data and mapping responses to the correct organizational units.

For a complete description of the table structure and field explanations, please refer to the → OrgStructureMaster 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.

This column captures the unique identifier of the client to which the organizational structure belongs.

1. Ensure that the client ID exists in the Clients Table.
2. This field is essential to link the organization structure to the appropriate client.

Example: clientid = 1

The label represents the name or title of the organizational unit,

This label will be visible in reports and organizational hierarchies.

Example: label = “Cluster A”

The heirarchy column determines the parent-child relationship of the organizational structure. It references the id of the parent organization unit.

1. If the unit has no parent, set the value to 0 (for top-level units).
2. For child units, enter the id of the parent unit.

Example:

In this example, Location 1 is a child unit of Cluster A.

The heirarchylevel column defines the depth level of the organizational unit.

1. 1 → Top-level units (e.g., Cluster)
2. 2 → Second-level units (e.g., Location)
3. 3 → Lower-level units, if applicable

Example:

This column determines if the organizational unit is used for evaluation purposes in survey reports.

If you want responses to be mapped to a specific organizational unit for evaluation, set the value to 1.

Example: usedforevaluation = 1

The createdby column captures the ID of the user who initially created this record.

1. This is usually linked to the User Table.
2. Ensure a valid user ID is entered.

Example: createdby = 996

The createdon column records the timestamp of when the organizational unit was created.

1. Format: YYYY-MM-DD HH:MM:SS
2. This is usually generated automatically if using the platform.

Example: createdon = 2022-05-26 07:27:17

The modifiedby column captures the ID of the user who last modified this record.

• If no modifications have been made, the value remains null.
• Otherwise, enter the valid user ID of the modifier.

Example: modifiedby = 996

The modifiedon column records the timestamp of when the organizational unit was last modified.

1. Format: YYYY-MM-DD HH:MM:SS
2. If never modified, the value will remain as 0000-00-00 00:00:00.

Example: modifiedon = 2023-09-07 15:58:13

Always ensure the client ID is correct to avoid mismatched data. Top-level units should have heirarchy = 0 and heirarchylevel = 1.

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

This structure would represent a client with one cluster and one location under it.