# Reusable or Dynamic Select Options in Custom Fragment Configuration

**URL:** <https://discuss.liferay.com/t/reusable-or-dynamic-select-options-in-custom-fragment-configuration/449>\
**Category:** Product Ideas\
**Tags:** fragments\
**Created:** [March 23, 2026, 10:09am UTC](https://discuss.liferay.com/t/reusable-or-dynamic-select-options-in-custom-fragment-configuration/449 "2026-03-23T10:09:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jconrad](https://avatars.discourse-cdn.com/v4/letter/j/85e7bf/32.png) [@jconrad](https://discuss.liferay.com/u/jconrad)\
**Post date:** [March 23, 2026, 10:09am UTC](https://discuss.liferay.com/t/reusable-or-dynamic-select-options-in-custom-fragment-configuration/449/1 "2026-03-23T10:09:04Z")

</div>

**What is the problem you are trying to solve?**

When creating a Custom Fragment in Liferay, it is possible to define a Select field in the JSON configuration (see: [https://learn.liferay.com/w/dxp/development/developing-page-fragments/reference/fragment-configuration-types-reference#select-configuration](https://learn.liferay.com/w/dxp/development/developing-page-fragments/reference/fragment-configuration-types-reference#select-configuration)).

Currently, the options for the Select field must be defined manually, for example:

```json
"typeOptions": {
  "validValues": [
    { "value": "1" },
    { "value": "2" },
    { "value": "3" }
  ]
}

```

The issue is that when the same Select field is used across multiple Custom Fragments, this configuration has to be duplicated in each fragment. As a result, any change (adding, removing, or updating an option) requires updating all fragments individually.

It would be nice to have a way to:

- Dynamically populate the Select options (e.g., from a centralized source), or

- Define the Select configuration once in a single location and reuse it across multiple fragment configurations.

**What is your project about? (e. g. Intranet, Partner Portal, Enterprise Website, etc)**

Enterprise Website

**What is your proposed solution? (optional)**

…

---

<div class="post-metadata">

**Author:** ![Luiz\_Jardim](https://dub1.discourse-cdn.com/flex014/user_avatar/discuss.liferay.com/luiz_jardim/32/304_2.png) [@Luiz\_Jardim](https://discuss.liferay.com/u/Luiz_Jardim)\
**Post date:** [March 30, 2026, 12:57pm UTC](https://discuss.liferay.com/t/reusable-or-dynamic-select-options-in-custom-fragment-configuration/449/2 "2026-03-30T12:57:50Z")

</div>

Thanks for your feedback, did you try to leverage picklists for this as well?

---

<div class="post-metadata">

**Author:** ![jconrad](https://avatars.discourse-cdn.com/v4/letter/j/85e7bf/32.png) [@jconrad](https://discuss.liferay.com/u/jconrad)\
**Post date:** [March 31, 2026, 6:38am UTC](https://discuss.liferay.com/t/reusable-or-dynamic-select-options-in-custom-fragment-configuration/449/3 "2026-03-31T06:38:41Z")

</div>

Hi Luiz,

I thought picklists were primarily meant for Custom Objects.  
As things stand, I don’t see how I could use picklists in the configuration (JSON) part of a custom fragment.

Could you clarify what you had in mind?