It looks like Custom Objects supports only string, integer, boolean and number types. We need to add an element to our custom object that is essentially a picklist but it seems like we cannot do this without hardcoding. I get the following error:
{"errors":[{"code":"BadRequest","status":"400","title":"Bad Request","detail":"data.schema object instance has properties which are not allowed by the schema: [\"enum\"]"}]}
How are people working around this limitation?
Hey @jena11,
Can you provide a copy of your request for me to take a look at? Let me know if you'd like to pull this into a ticket.
Thanks!
Hey @eric27
Thanks for following up! I did submit a ticket already and was directed to this community instead. Unfortunately, given the lack of response I have chosen to move forward with a different product's toolset so no need for further triage.
Thanks.
Hey Ahmed.. Unfortunately, we don't support enum. But thank you for calling out the discrepancy in documentation. I will get that updated. But the good news is that, we are working on a newer version of custom objects, which will include all the field types that a User or an Organization supports today. And will also work seamlessly with other Zendesk products like Triggers, Tickets etc. We intend to release this new version in the first half of next year.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry to hear about your less than ideal experience. We're a pretty small team that covers the community so it sometimes takes us a bit to get to every post.
Let us know if you need anything,