Skip to main content

A configuration will not save (No schema)

Select the config, Save Configuration, confirm Success, then fix schema on templates if needed.

Written by Ryan Miller

Use this when you cannot save a configuration on the Cloneable web portal, changes vanish after refresh, or fielders see No schema configured on chip or photo fields in UtilityScout. You'll need org-admin access to Configuration Manager, since only an admin can attach the correct schema on templates to clear that error.

Save the configuration

  1. Open Configuration Manager and confirm a configuration is selected before you edit. Steps stay hidden until a config is selected.

  2. Ensure the configuration has a name. Save stays disabled when the name is empty (or while saving).

  3. Click Save Configuration. Wait for Saving... then a Success toast (wording may say Configuration saved successfully).

  4. Refresh and re-open the configuration to verify your changes stuck.

  5. Incomplete templates or triggers do not block Save, but finish them before fielding so import and field flows work. Save Field Options changes the same way when you change those toggles.

  6. If recreating a config, avoid a name that matched an archived one - use a new name or ask support.

  7. If fielders see No schema configured on chips or photos: an org admin must attach the correct companion schema on the configuration templates, then save and re-check the field UI.

If something goes wrong

  • Schema error remains after the config looks complete → escalate with a screenshot of the field error.

  • Include what you were editing, whether Save produced a Success toast, and (for field schema errors) a Utility Map job link plus object link. See What to send.

Important: Success toast never appears, or save errors persist → Create a ticket.

Next: finish setting up your configuration so its templates and schema are complete. See Set up your configuration, stage by stage.

Did this answer your question?
Cloneable Help Center