Skip to content

Blueprints and moving forms between orgs

A blueprint is a form saved as a file. It holds the form’s settings and all its questions and blocks, in order. Use it to:

  • move a form from a sandbox to production,
  • keep a copy of a form in version control,
  • give a form to another organisation’s Salesforce org.

The Share tab in the builder with the Download button for the blueprint

  1. Open the form in the Form Builder.
  2. Click an empty part of the canvas so nothing is selected, then open the Share tab.
  3. Click Download.
  4. Keep the file in version control, or send it to the admin of the org you are moving it to.

Versions matter. A blueprint downloaded from an org on a newer version of Sliick Forms is refused by an org on an older one, with a message that it was written by a newer version of Sliick Forms. Upgrade the receiving org first. Going the other way, a blueprint exported before version 1.0 cannot be imported into 1.0 or later: export it again from the upgraded form. See Upgrading the package.

The blueprint import summary showing the form was updated and one element was removed

  1. Go to the Sliick Admin Dashboard.
  2. In the Forms toolbar, click Import blueprint and choose the .json file.
  3. Read the summary. It says whether the form was created or updated, how many questions and blocks it now has, and how many were removed.

Import replaces, it does not add. If the blueprint leaves out a question or block that exists on the form in this org, that question or block is deleted. Always check the delete count.

A broken blueprint is refused, and nothing is changed. If the file describes a form that could not display properly, the import stops, names the blocks involved, and writes nothing. For example, a page or section that starts inside a repeating group, or an End Repeat with no matching start. Fix the file and import again.

Each form and each question has an external ID. Importing a blueprint updates the matching form and questions by that ID. If a question has no external ID, import cannot match it, so it is added as a new question.

A blueprint can also carry a few settings the builder does not show, such as a question’s own link parameter name, and theme colour values the builder’s colour pickers would not produce. See Colours, fonts and logos.

Allow on your public Sliick Edge address is not in a blueprint, because it belongs to your org’s address, not to the form. A form created by import starts with it off. Importing over an existing form leaves the setting as it was. See Hosting on Sliick Edge.

  1. Keep the external IDs of forms and questions the same in every org.
  2. Never rely on Salesforce record IDs to move forms between orgs.
  3. Export from a known-good org before making large changes elsewhere.
  4. Check the delete count after every import.
  5. Keep blueprint files in version control, so you have a history of changes outside Salesforce.