preignition/program-user-docs
accessiblesurveys
  • TRAINING COURSE
    • Introduction
    • Session 1- Creating a new survey
    • Session 2- Adding accessibility options to a Form
    • Session 3- Translating a Form into different languages
    • Session 4- Sharing your survey using the Survey Editor
    • Session 5- Analysing your survey responses and exporting your survey data
  • TUTORIALS
    • Introduction to creating a new survey
    • Introduction editing a form
    • Introduction to testing a form
    • Introduction to publishing a form
    • Introduction to Easy Read
    • Introduction to Sign Language
    • Introduction to form logic
    • Introduction to the Customer Portal
  • GUIDANCE NOTES
    • Survey App
      • Creating a new survey
      • Form Editor
        • Structuring a form
        • Adding questions to a form
          • Text based questions
          • Choice based questions
          • Rating, Slider, Order and Range questions
          • Media based questions
          • Introduction to free text fields
        • Testing a form
        • Publishing a form
        • Introduction to form logic
        • Advanced form logic
        • Using tooltips
        • Using Markdown
        • Adding an accessibility menu
        • Form Behaviour
        • Image Library
        • Easy Read
        • Sign Language
        • Translate forms
        • Using import/ export to translate forms
        • Access rights for forms
        • Sharing options across multiple questions
      • Survey Editor
        • Editing a survey
        • Distributing your survey
        • Survey respondent accounts
        • Redirection after completing survey
        • Language settings for surveys
        • Creating alias survey links
        • Survey batches
        • Presenting surveys
        • Survey access rights
        • Survey terms- advanced
        • Publishing surveys
      • Analytics
        • Introduction to survey analytics
        • Exporting Survey Data
    • Customer Portal
      • Portal
        • Profile
        • Subscription
      • Team
      • My Profile
      • Users
      • Using labels
  • FAQ
    • Data privacy and security
      • Why and how do we collect data?
      • How do we protect data?
      • What is GDPR?
      • What rights do individuals have under GDPR?
      • What obligations do controllers have under GDPR?
      • What obligations do processors have under GDPR?
      • Where is data stored?
      • How can I ensure that my surveys GDPR compliant?
      • How to Write GDPR-proof Privacy Policy for your Surveys
    • What is the best image size, ratio and format?
    • How to use free text
      • Convenient Class for Accessible Surveys Free Text Field
      • CSS tokens available in Markdown Free Text
      • Web-components available in Markdown Free Text
      • Accessibility Modes
    • FAQ about the Form Editor
      • How do I resolve warnings when publishing a form?
      • How can I get feedback about my survey?
    • Guide to producing Accessible Surveys
      • Producing your survey in Plain Language or Easy to Read
      • Producing your survey in sign languages
    • FAQ about survey data and analytics
      • How do I ensure that the data in my CSV file is properly formatted?
  • Release Notes
    • Form Builder
      • import/export
      • Section Container
    • Process Builder
    • Reporting
    • Survey
  • API
    • survey
    • member
Powered by GitBook
On this page
  • Introduction
  • Resolving the issue
  1. FAQ
  2. FAQ about the Form Editor

How do I resolve warnings when publishing a form?

PreviousFAQ about the Form EditorNextHow can I get feedback about my survey?

Last updated 1 year ago

Introduction

When publishing a new version of a form, the application runs checks to make sure that the form has been built successfully.

If the build has not been sucessful you will see the message 'Build completed with warnings'.

Double clicking on the row provides details of what is causing the problem, along with a link to the item which is causing the problem.

Resolving the issue

The most common issue encountered, is when two or more questions have the same 'code'. This is important as a question's code determines where answers to the question are stored on the database.

By default a question's code is derived from it's label. This has the advantage of making the database structure easy to navigate. However problems arise when question labels share the same first twenty characters.

This issue can be resolved by editing the question's code so each question has a unique code.

  1. First activate the 'advanced' tab

  2. Click into the question refered to in the warning section

  3. Give the question a unique 'override code' up to a maximum of 20 characters

  4. Publish a new version of the form and check that the build has been completed successfully

20 second video showing a from being published with warnings
30 second video showing how to resolve a common issue with questions having the same code