Skip to main content

Fix Issues with Project-Level Variables

This guide helps you troubleshoot and resolve problems that may occur when working with variables in a specific project. Use it if a variable doesn’t populate as expected, appears incorrectly in documents or forms, or cannot be edited.

When to Use This Guide​

You Should use this guide if:

  • A variable displays incorrect or missing data.
  • The value format doesn’t match what your form or template expects.
  • You’re unable to edit a variable even though it exists in the project.

Common Issues and How to Fix Them​

Use this section to resolve common problems when working with project-level variables.

Variable does not populate​

  • Missing value: Ensure the variable has a value set in the project-level Variables tab.
  • Incorrect key: The variable’s key must exactly match the merge field used in forms and documents (e.g., {{projectName}}).
  • Field type mismatch: If the variable pulls data from another source (e.g., Project Content), verify the source is selected.

Incorrect or outdated value​

  • Review the current value and update it if it was copied from another project or left unchanged from a template default.
  • Check if the variable is meant to be updated manually or by form input.

Formatting issues​

  • Ensure the value matches the expected data type (e.g., text, number, date, currency, dropdown).
  • Dropdown and radio values must match one of the available options; otherwise, the field may appear empty or fail to load.

Unable to edit the value​

  • Permissions: Editing variables may be restricted to certain user roles. Contact your workspace admin if needed.
  • Locked workflow stage: If the variable is tied to a completed or locked stage, it may need to be reopened before edits are allowed.

Edits made to variables at the project level only apply to that specific project. They don’t affect templates.

See Also​

To complement your knowledge of this process, check the following pages: