# Allow for a value within HubDB select and multi-select fields.

**URL:** <https://community.hubspot.com/t/allow-for-a-value-within-hubdb-select-and-multi-select-fields/40648>\
**Category:** HubSpot Ideas\
**Tags:** design-manager\
**Created:** [July 13, 2021, 2:37pm UTC](https://community.hubspot.com/t/allow-for-a-value-within-hubdb-select-and-multi-select-fields/40648 "2021-07-13T14:37:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tstrack](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tstrack/32/74736_2.png) [@tstrack](https://community.hubspot.com/u/tstrack)\
**Post date:** [July 13, 2021, 2:37pm UTC](https://community.hubspot.com/t/allow-for-a-value-within-hubdb-select-and-multi-select-fields/40648/1 "2021-07-13T14:37:47Z")

</div>

It’d be great if the select + multi-select fields in HubDB had both a “pretty” name and a value. For example, in my attached screenshot, **Agriculture Farming** would be the “pretty” name and **agriculture\_farming** would be the value. Or **Oil, Gas, & Energy** would be the “pretty” name and **oil\_gas\_energy** would be the value. I often use these fields for filtering via a custom module and the pretty names make it a pain. ACF in WordPress does a really good job of this offering both a pretty and value as a return format.

 ![Screen Shot 2021-07-13 at 8.13.03 AM.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/8/4/8421a3c8c4a3c1a748d4f76f6b1534fd07590877.png)

---

<div class="post-metadata">

**Author:** ![awright415](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/awright415/32/70551_2.png) [@awright415](https://community.hubspot.com/u/awright415)\
**Post date:** [July 13, 2021, 3:32pm UTC](https://community.hubspot.com/t/allow-for-a-value-within-hubdb-select-and-multi-select-fields/40648/2 "2021-07-13T15:32:03Z")

</div>

Probably worth mentioning that _both_ values should be available in HubL. (AFAIK, they aren’t when using choice fields in custom modules.)