Lua Scripting Resources

Important Update to Custom Scripting

SurveyGizmo's CustomScript Action now supports the LUA programming language.


Legacy Custom Scripting Language Deprecation Plans 

  1. New accounts (created after October 29, 2018) will only have the option to use Lua in scripts.
  2. As of October 29, 2018 Custom Scripting Actions will default to Lua as the scripting type in the Custom Scripting Action for accounts created before this date. You will be able to switch to the Legacy Custom Scripting; though we highly encourage using Lua.
  3. In the long term, Legacy Custom Scripting Actions will be switched to read-only. Read-only scripts will continue to function; you will just be prevented from editing. The exact date on this is to be determined; we will send notifications well ahead of time.


 Go to our Legacy Scripting Documentation.

While SurveyGizmo is one of the most flexible survey tools around, we get requests for customizations that are not available out of the box. This is where JavaScript and Custom Scripting can save the day. If you have scripting chops you can use the JavaScript action or the Custom Scripting action to achieve the survey of your dreams.


[article("bodfy")]

By default, hidden values do not update when respondents go back in a survey and change their answers. One way to solve this problem is to remove the Back button on a survey, but that still doesn't ensure that they can't click Back on their browser. If you need to ensure that hidden values get updated, use this script.

Features and functions used in this script:

The Script

Copy and paste the following code in a Custom Script action. Make sure the action is on a page that follows the question from which the hidden value pulls. The hidden value must follow the script but it can be on the same page.  

--[[Reset a hidden value when a respondent changes their answers.
Place this script above the hidden value you are changing (on the same page)
--]]

-- The merge code or codes that are going to be evaluated. This is usually the same merge code as that in the hidden value
mergeCode = '[question("value"), id="2"]'
-- The ID number of the hidden value you are changing
hiddenValue = 4

---------- Be careful editing below this line ----------

setvalue(hiddenValue, evaluatemergecodes(mergeCode))

Required Customizations

Change the ID for the merge code that is going to be evaluated and the ID of the hidden value.