What changes
- Every question and answer option gets a code. A data migration gives each question the next unused
q1,q2, … and each answer option, matrix row and matrix column a code1,2, … in today’s order. It runs with the other database migrations during the upgrade. It doesn’t rename Question IDs, reorder anything or change stored responses. See question codes. - A published survey is locked. Once a survey leaves draft (active, paused, completed or scheduled), the server refuses a save that changes a question code, an answer code, a question type or an option’s text in any language, or that deletes an option that existed at launch. Adding questions and options still works.
- The Excel file of the Standard export names its sheet
Response Datainstead ofSheet1. - Webhook payloads gain two keys,
dataByQuestionCodeandoutcome. Existing keys stay.
Before you upgrade
The lock applies to the survey editor,
PUT /api/v1/management/surveys/{surveyId}, PATCH /api/v3/surveys/{surveyId},
the v3 block routes and the MCP survey tools. Clients that only read surveys, send unchanged values or edit
draft surveys are not affected.
Working with the lock
- Fix typos and translations before you activate a survey. The editor has no unlock.
- To change an option’s wording on a live survey, add a new option with the new text.
- If a script must change a locked field, set the survey back to
draft, make the change and publish it again. Responses already collected keep the old text, and the Analysis export lists answers that no longer match an option as unmapped values. The lock protects the meaning of exported data; it isn’t a security control.