Skip to main content

Resolving “Type Already Exists” Errors

Learn why you may receive a “Type already exists” error when creating Booking Types, Event Types, or Market Segments in a Chain account, and how to update Organization access to resolve it.


If you receive an error stating that a Booking Type, Event Type, or Market Segment already exists when trying to create one, the Type may already be configured at the Chain level or assigned to another Organization within your Chain.
​

Why Is This Happening?

For Chain accounts, certain settings can be managed centrally and shared across multiple Organizations. A Type may already exist at the Chain level but be assigned only to specific Organizations.
​

As a result, you may receive an error when trying to create a duplicate Type, even if you cannot see it in your Organization's active or archived settings.
​

How to resolve this: A user with Chain Admin access will need to update the existing Type's Organization assignments to include your Organization, or make the Type available to all Organizations, as appropriate.


How to Update Organization Access

Booking Types

  1. Go to Settings.

  2. Click Fields.

  3. Select Booking Types.

  4. Find the existing Booking Type and click Edit.

  5. Select the Organizations that should have access to the Type, including your Organization.

Save your changes.
​


Event Types

  1. Go to Settings.

  2. Click Fields.

  3. Select Event Types.

  4. Find the existing Event Type and click Edit.

  5. Select the Organizations that should have access to the Type, including your Organization.

Save your changes.
​


Market Segments and Other Types

If you're receiving this error when creating a Market Segment, Booking Type, or Event Type, ask your Chain Admin to review the existing Type's Organization assignments and update them to include your Organization, where appropriate.
​

If the existing Type cannot be located or the error persists after updating the assignments, contact Event Temple Support for further assistance.

Did this answer your question?