Skip to main content

Configuration & Advanced Tools

These messages appear mainly to power users and administrators while configuring templates, forms, charts, schemas, and settings (for example in Design Studio). Everyday users rarely see them. If you do see one and you are not the person configuring the system, the answer is almost always to contact your administrator.

For the full guidance on collecting details and choosing who to contact, see the Overview.

Template & form configuration​

Validation prompts when saving a template​

These tell you a required field is missing or invalid — fix the named field and save again:

  • "Template name is required."
  • "Template display name is required."
  • "Template type is required."
  • "Type is required."
  • "Template name must be 255 characters or less."
  • "Template display name must be 255 characters or less."

"Failed to save page template configurations." / "Failed to load page template configurations."​

  • What it means: A page template could not be saved or loaded.
  • What you can do:
    1. Refresh and retry.
    2. For a save failure, re-check every required field is completed.
    3. Check your connection.
  • If it keeps happening: Note the template name and the action, plus the date/time, and take a screenshot. Escalate to Protrak Support if configuration is correct but saving still fails.

"Voice Form Configuration only supported in Global Scope."​

  • What it means: Voice form configuration can only be done at the global scope, not the scope you are currently in.
  • What you can do: Switch to the global scope to configure the voice form.

Empty states while configuring​

Normal messages meaning there is nothing to choose from yet — create or configure the relevant item first:

  • "No form widget is available."
  • "No layout templates are available. Contact system administrator."
  • "No type widgets are available in this page template."
  • "No page templates found"

Charts​

"No picklist options found for the selected attribute."​

  • What it means: The attribute chosen for chart colours has no picklist values to map colours to.
  • What you can do: Select an attribute that has picklist options, or add options to the attribute first.

"No colors configured. Add state values to configure colors."​

  • What it means: No colours have been set up yet for the chart.
  • What you can do: Add the state values you want to colour, then assign colours.

Schema & user import/export​

These are administrator tools. When one fails:

  • "The schema could not be exported." / "Failed to export schema."
  • "The schema could not be imported." / "Failed to import schema."
  • "Failed to import users." / "Failed to export users."

For a schema import specifically, the notification usually also includes the exact reason it failed (a duplicate name, a file that was too large, and so on) right after this message — see Importing a Schema for what these mean and how to fix them.

What you can do:

  1. Retry the operation.
  2. For an import, confirm the file is a valid, unmodified export and matches the expected format.
  3. Try a smaller file to isolate whether size or content is the problem.

If it keeps happening: Keep the exact file involved. Provide it along with the date/time and a screenshot to Protrak Support — schema and bulk-user operations are the kind of issue Support is best placed to investigate.

Settings & cache​

"The settings could not be loaded." / "The settings could not be changed."​

  • What it means: A settings screen could not load or save.
  • What you can do: Refresh and retry; check your connection. If it persists, report it to Protrak Support with the setting and the date/time.

"Unable to clear cache. Please try again." / "Tenant information is unavailable. Please refresh and try again."​

  • What it means: A cache-clear or tenant utility action did not complete.
  • What you can do:
    1. Refresh and try again.
    2. Confirm your connection is stable.
  • If it keeps happening: Report it to Protrak Support with the date/time and a screenshot — these are administrative operations that Support can investigate against the server logs.

Preview and widget configuration (Design Studio)​

While building layouts you may see:

  • "Failed to load widget configuration"
  • "Failed to load preview data."
  • "Failed to fetch related types. Please try again."
  • "Failed to fetch instance details"

What you can do: Retry, refresh the editor, and confirm the underlying type/widget/record you are previewing still exists and is configured. If a preview consistently fails for a valid configuration, capture the diagnostic details and report it to Protrak Support.