With all the changes to the Custom Objects over the last couple of years (placeholders are an AWESOME addition), we are finding that we want to use Custom Objects for a lot more things, but we cannot because we are at our limit for 10 lookup relationship fields on our ticket form. Increasing this limit could open up a world of possibilities for us. Given the increased utility of custom objects, are there any plans to raise the lookup relationship limits so that we can take fuller advantage of these great features?
Idea Submitted
Lookup Relationship Field Limit Increase
Definitely a need for more lookup fields. Have hit this limitation a number of times and have to revert to a static dropdown field to get what we want, reducing the functionality of Zendesk and increasing the static field management overhead for these processes.
Also, enabling SLAs to leverage lookup fields in policy conditions would be great.
It would be amazing to see an increase to the number of lookup fields.
In our case, we maintain a large SKU catalogue that needs to be referenced across multiple ticket forms. Because we can’t add additional lookup relationship fields, we’ve had to duplicate the same SKU lists across multiple drop-down fields and forms to cover different workflows. If there is any chance this could be updated, that would be greatly appreciated..
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Thank you for taking the time to provide us with your feedback. This has been logged for our PM team to review. For others who may be interested in this feature request, please add your support by upvoting this post and/or adding your use case to the comments below. Thank you again!