Custom Object Reports in Zendesk explore | The place for Zendesk users to come together and share
Skip to main content
Feedback submitted

Custom Object Reports in Zendesk explore

Related products:Support
  • February 18, 2025
  • 3 replies
  • 41 views

Evangelina11

1. We have many custom object lookup fields but due to this limitation mention in this article

https://support.zendesk.com/hc/en-us/articles/4408824384538-Reporting-with-custom-fields?Z2_EN-US%5Bquery%5D=custom%20object#topic_glv_tww_23b

We are unable to report of custom object lookup fields.

2. The custom object records page is limited in its display options. Currently, it only shows the default columns: Name, Created at and Last updated
It does not provide the ability to add other object fields as columns for viewing.



 

3 replies

Shawna James
  • Community Manager
  • February 20, 2025
Hello Evangelina, 
 
Thank you for taking the time to provide us with your feedback. This has been logged for our PM team to review, and for future reference, here’s our product feedback template. This template has been designed by community members and PM's to help users provide the most accurate details for their feature request so that we can better understand your use case and needs. You do not need to update your post now but we would appreciate it in the future if you could utilize the template.
 
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!

  • Product Manager
  • July 4, 2025

Nick58
  • April 16, 2026

Adding my voice to this — the current state of custom object reporting in Explore is a real blocker for us.

We've built a bespoke shipping system in Zendesk using three custom objects: Shipments, Shipment Lines, and Parts. A Shipment has a lookup to the Ticket (so one ticket can have many shipments), and each Shipment Line has lookups to its parent Shipment and to a Part, plus a quantity. The structure works beautifully for agents in the workspace, but it's completely invisible to Explore because all of my lookups go "outward" from the custom objects rather than from the ticket.

I can't report on shipment volume, parts shipped, shipments per ticket, or anything else derived from this data without exporting via the API and analysing it in an external BI tool, which defeats a lot of the value of having it in Zendesk in the first place.

What I'd need to see:

  1. Custom objects available as primary datasets in Analytics/Explore, not just as related attributes hanging off tickets.
  2. Lookup relationships traversable in both directions (so a Shipment → Ticket lookup can still surface ticket attributes in a shipment-based report).
  3. Multi-hop relationships (so from Shipment Lines I can reach Shipment → Ticket on one side and Part on the other).

I’d love to see this prioritised. Custom objects are a headline feature of Suite, but without reporting they're an operational tool with no visibility layer.