Limitations of Zendesk Legacy Custom Objects
What are the limitations of legacy custom objects in Zendesk?
Legacy custom objects in Zendesk come with certain limitations. Each account can have a maximum of 50 legacy custom objects. The number of custom object records varies by plan: Support Enterprise, Suite Team, and Growth plans allow up to 100,000 records, Suite Professional allows 250,000, Suite Enterprise allows 1,000,000, and Suite Enterprise Plus allows 25,000,000.
These limitations are important to consider when planning how to use legacy custom objects in your Zendesk account, especially if you anticipate needing a large number of records.
More related questions
What are legacy custom objects in Zendesk?
Legacy custom objects in Zendesk allow you to create custom data objects tailored to your business needs. They can represent anything from products to service contracts. You can create these objects in the Zendesk Admin Center or via the API, and…
How do I enable legacy custom objects in Zendesk?
Legacy custom objects are only available to accounts that enabled the feature before September 2023. If you haven't enabled them by then, you'll need to explore the new custom object experience. For those with access, legacy custom objects can be…
How can I define a legacy custom object type in Zendesk?
To define a legacy custom object type in Zendesk, you need to create a blueprint called an object type. This involves specifying a key and a schema that describes the attributes of the object. For example, a 'rental_property' object type might…
How do I add records to a legacy custom object in Zendesk?
To add records to a legacy custom object in Zendesk, developers can use the Sunshine API. The data included in the API request must match the attributes defined in the object type's schema. For example, a 'rental_property' record might include…
How can I model data with legacy custom objects in Zendesk?
Modeling data with legacy custom objects in Zendesk involves establishing relationships between different object types. For instance, you can create a relationship between a 'rental_property' object type and Zendesk tickets to associate customer…
How do I define a legacy relationship type in Zendesk?
To define a legacy relationship type in Zendesk, you create a blueprint for associating records between two object types. For example, you might define a 'rentalpropertyhasmanytickets' relationship type between a custom 'rental_property' object…
How can I associate related records of legacy custom objects in Zendesk?
Associating related records of legacy custom objects in Zendesk involves creating relationship records based on a defined relationship type. For example, you can link a specific ticket to a rental property using the…
How do I retrieve related records in Zendesk legacy custom objects?
To retrieve related records in Zendesk legacy custom objects, developers can use the List Relationship Records by Object Record endpoint. This allows you to access all related records for a specific object, such as tickets associated with a rental…
How can I set roles and permissions for legacy custom objects in Zendesk?
Setting roles and permissions for legacy custom objects in Zendesk allows you to control access to these objects. After saving the object schema, you can define permissions for agents and end users in the Permissions tab. By default, agents have…
How do I delete custom object types and relationship types in Zendesk?
To delete custom object types and relationship types in Zendesk, navigate to the Admin Center, select Objects and rules, and choose either Custom objects > Objects or Custom objects > Relationships. Hover over the type you want to delete and click…
Interested indeflectingover 70% of your Zendesk support tickets?
Zendesk Support Tickets
Zendesk Messaging (live chat)
Join1,000+ companies reducing their support costs and freeing up support agents for more important work
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
Reduce support costs.Spend more time on customer success.
