This guide provides a comprehensive step-by-step approach to correctly populate the fw_questionnaireheader table in the database. This table contains the core metadata and configuration settings for each questionnaire, defining how it behaves in both the backend system and the survey interface.

Each entry in this table represents a unique questionnaire with associated questions, start/end dates, configurations, and key control settings.

You can refer to the detailed structure of the QuestionnaireHeader Table here: → QuestionnaireHeader 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.

Example: - Leave this field blank when inserting data.

This field connects the questionnaire to a specific module in the modulesettingoptions table. It determines which module the survey belongs to.

Example: - For KTO Customer Survey: moduleid = 1001

Defines when the survey becomes active. Enter the date in the format: YYYY-MM-DD.

Example: - startdate = 2025-04-01

Defines when the survey expires. Ensure the end date is after the start date.

Example: - enddate = 2025-12-31

Tracks the last question ID the respondent answered. Leave this field blank if inserting manually — it is system-generated.

Example: - lastqdetailid = 34

Tracks the last option ID the respondent selected. Leave this blank when inserting manually — it is system-generated.

Example: - lastoptionids = 178

Lists option IDs that will be treated as anonymous. Separate multiple option IDs with a comma (,).

Example: - anonymousoptions = 123,124,125

Keeps track of how many anonymous invitations were sent. This count starts at 0.

Example: - anonymousinvcnt = 0

Specifies which action lists or data sets exclude identifiable respondent information. Provide option IDs separated by commas.

Defines the current state of the survey.

Allowed Values: - 1 = Active - 0 = Inactive - 2 = Archived

Defines which questions should be excluded from the survey. Provide question IDs separated by commas.

Example: - filterquestions = 43,47

Determines how many question tiles appear per page.

Example: - nooftilesperpage = 9

Defines how many columns should appear per page.

Example: - noofcolperpage = 3

Defines the option IDs that terminate the survey if selected. Separate multiple option IDs with commas.

Example: - optoutoptionids = 100,101

Defines the primary language conversion for the survey. This is useful for multi-language surveys.

The `branchlevelqtnposition` field is used to:

• Group questions under section headers.
• Define the display order of branch-level questions.
• Create separate navigation menus per section.

click here to learn more in detail

Stores the menu ID for branch-level questions. Identifies the section where the question will appear.

Example: - 80,81,82,83,84^|||^Position1~^|^~Position2~^|^~Position3~^|^~Position4~^|^~Position5^|||^80,81,82,83,84

Defines the maximum number of tags displayed in the tag cloud.

Example: - maxtags = 50

Defines how often a word must appear to qualify as a tag.

Example: - tagfrequency = 5

Ensures each word from a respondent is counted only once in the tag cloud.

Example: - counttagonce = 1

Links to a referenced question detail ID for tailor-made questions. This automatically updates dispcndtn and dispprms.

Example: - vraagreferenceqdetailid = 234

Defines the question detail IDs linked to emotion-related questions. Separate by commas.

Example: - emotionqdetailids = 45,67,89

Allows default text to display if graph content is empty.

Defines the number of open-ended answers to include in the export.

Example: - noofopenansinexport = 100

Specifies the type of emotion library used.

Defines the type of topic library.

Example: topiclibrarytype = modules/ennatuurlijk

Stores the version of the topic library.

Example: topiclibraryversion = v1.0

1. Always verify that the lastqdetaillid and lastoptionids are correct when there are changes in the existing module.
2. Always verify that the startdate and enddate are valid.
3. For opt-out options, ensure those options terminate the survey if selected.