In this article
Special surveys are used to update the panelist information. These surveys will need to contain a number of scripting objects that are used to perform particular functions within the panel database - .
Figure 1 - Example of a simple Panelist Update survey
Fetching the Existing Information
When a panelist wishes to update his/her information, the first operation the survey must perform is to fetch the existing data from the database. This will then be used to populate the survey so the panelist can see the current information.
Note: If the password is fetched, it can be updated but for security reasons it will be encrypted such that it cannot be read.
The first object in the survey will therefore be a script object to fetch the data. This will need a script, for example that shown in the figure below - .
Figure 2 - Example of script to fetch the data from the database
Updating the Existing Information
As when registering a new panelist, the database must be updated with the information. This will require an “Update” script object in the survey, containing a script such as that shown in the figure below - .
Figure 3 - Example of script to update existing panelist information
Note: If the password is one of the fields fetched, a validation check is performed. If the check fails, the update will not be performed. Note also that for security reasons the password will be encrypted such that it cannot be read.
Removing Respondent Data from the Survey
As when registering a new panelist, once the database is updated, the current respondent information must be removed from the survey to prevent database overload. And again, a redirect script is required to prevent the survey returning an error when it notices that it contains no data for the current respondent - .
Figure 4 - Example of script to delete the response and redirect