# Get \*All\* Values of a Custom Object from crm\_objects Function

**URL:** <https://community.hubspot.com/t/get-all-values-of-a-custom-object-from-crm-objects-function/122933>\
**Category:** CMS Development\
**Tags:** professional\
**Created:** [December 22, 2024, 6:03pm UTC](https://community.hubspot.com/t/get-all-values-of-a-custom-object-from-crm-objects-function/122933 "2024-12-22T18:03:33Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![thekevinpotts](https://avatars.discourse-cdn.com/v4/letter/t/9de0a6/32.png) [@thekevinpotts](https://community.hubspot.com/u/thekevinpotts)\
**Post date:** [December 26, 2024, 4:17pm UTC](https://community.hubspot.com/t/get-all-values-of-a-custom-object-from-crm-objects-function/122933/4 "2024-12-26T16:17:11Z")

</div>

OK, I discovered that the function MUST include more information, which I did not sufficiently explore in my initial tests. Custom objects seem to be unique in this regard. Whereas the crm\_objects function calls a full array for _standard_ HubSpot objects, crm\_objects must include a filter and the names of the properties being called.

In other words, this works as expected:

```lia-code-sample
{% set webinars = crm_objects("webinars", "limit=5","webinar_title,slug,date_and_time,short_description") %}
{{ webinars|pprint }}

```

This will then give me a full array with the title, url slug, date and time, and my summary, all of which are custom properties.

---

_[View the full topic](https://community.hubspot.com/t/get-all-values-of-a-custom-object-from-crm-objects-function/122933)._