> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nextedy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Offer Resources in a Custom Field

> Point a Polarion custom field at your resource work items with the Nextedy Resource enumeration from Nextedy GANTT, so every field using it in a project picks from one resource pool you define once.

The **Nextedy Resource** enumeration turns resource work items into the options of an ordinary Polarion enumeration field. You say once what a resource is and where the resources are held, and every custom field in the project that uses the enumeration offers that pool — including resources held in a project of their own, with no extra cross-project enumeration extension. Available since version **26.10.0**.

The enumeration is a flat list. It shares no configuration with the [hierarchical resource picker](/gantt/guides/resources/hierarchical-resource-picker.md): you can use either on its own, or both on different fields. For how the two compare, see [Resource Breakdown Structure](/gantt/concepts/resource-breakdown-structure.md#a-flat-list-the-resource-enumeration).

## Prerequisites

Before you begin, ensure that:

* Gantt is installed — the enumeration is part of it
* Your resources exist as Polarion work items, for example of a work item type `resource`
* You have administrator rights on the project that will carry the field, with write access to its administration, so you can set configuration properties and add custom fields

**1. Define Which Work Items Are Resources**

In **Administration > Configuration Properties** of the project that will carry the field, set the Lucene query that selects your resources:

```properties theme={null}
nextedy.gantt.resourceEnum.query=type:resource AND project.id:ResourceBreakdown
```

The query is used exactly as written — nothing is added to it. Say there both what a resource is and which project holds them; with no project clause, matching work items from every project are offered.

Leave the property unset and the enumeration offers every work item of type `resource`, the default query `type:resource`.

**2. Choose What Is Stored, if Not the Work Item ID**

By default, the value stored on a work item is the resource's work item ID. To store a different identifier — a resource code or personnel code held in a string field of the resource work item — name that field:

```properties theme={null}
nextedy.gantt.resourceEnum.idField=resourceCode
```

The field must be a string field. Every resource then needs a value in it, unique among the resources the query returns.

> [!WARNING]
>
> **Set It in Both Projects**
>
> When the resources live in another project, set `idField` to the same value in the project carrying the field **and** in the project holding the resources. The stored value is taken from the field the resource's own project names, but a value is looked up again through the field the carrying project names — where the two differ, the field cannot find the resource it stored.

**3. Add the Custom Field**

1. Open **Administration > Work Items > Custom Fields** and select the work item type that should carry the field.
2. Add a field — for example `resource`, named **Resource** — of type **Enum**.
3. In the enumeration list, select **Nextedy Resource**.
4. Click **Save**.

![The Custom Fields Designer for the Task type, with a Resource field of type Enum and its enumeration list open on Nextedy Resource](https://mintcdn.com/none-17b4493f/DdW9lQRJzLmUSR5w/gantt/images/offer-resources-in-a-custom-field/custom-field-nextedy-resource.png?fit=max\&auto=format\&n=DdW9lQRJzLmUSR5w\&q=85\&s=16bb52fb181ec487d430b0ce3c165e11)

The **Nextedy Resource** enumeration takes no query of its own on the field: what it offers comes from the configuration properties above, so every field using it in the project offers the same pool.

If the work item type has its own form layout, add the field to it as well — a field the layout does not list is not shown on the work item form.

**4. Pick a Resource**

Open a work item of that type, click **Edit**, and open the **Resource** field. It lists the resources the query returns, each by its title, sorted by project ID and then by title.

![A task in edit mode with the Resource field open, listing six resources by title in alphabetical order](https://mintcdn.com/none-17b4493f/DdW9lQRJzLmUSR5w/gantt/images/offer-resources-in-a-custom-field/resource-field-options.png?fit=max\&auto=format\&n=DdW9lQRJzLmUSR5w\&q=85\&s=b0ec88e21a5d50522c40049d1a4e898a)

Select one and click **Save**. The work item must be saved for the selection to be stored; close it without saving and the field keeps its previous value.

![The saved task showing Firmware Team in its Resource field](https://mintcdn.com/none-17b4493f/DdW9lQRJzLmUSR5w/gantt/images/offer-resources-in-a-custom-field/resource-field-saved.png?fit=max\&auto=format\&n=DdW9lQRJzLmUSR5w\&q=85\&s=af6f9bce41bb48857975285c7e97e550)

## Large Resource Pools

The enumeration lists every resource the query returns and never truncates the list. Resources in different projects that share a work item ID appear only once, so scope the query to the project holding your resources. That suits a pool of tens or hundreds of resources. For a pool in the thousands — or tens of thousands of nodes — a flat list is not usable in the browser; narrow the query, or use the [hierarchical resource picker](/gantt/guides/resources/hierarchical-resource-picker.md), which browses the structure one level at a time.

## Troubleshooting

| Symptom | Cause | Fix |
| - | - | - |
| The field offers work items that are not resources | The query is too broad — it is used as written | Add the type and project clauses to `nextedy.gantt.resourceEnum.query` |
| The field offers nothing | No work item matches the query, or the default `type:resource` does not match your type ID | Check the query in Polarion's own search, then set it in `nextedy.gantt.resourceEnum.query` |
| A saved value no longer shows its title | The resource no longer matches the query, was removed, or its `idField` value changed | Restore the resource or its identifier, or pick the resource again |
| Values saved before setting `idField` stop resolving | They store work item IDs, while the field now looks resources up by the new identifier | Pick the affected resources again after changing `idField` |

## Verification

You should now see:

* **Nextedy Resource** selected as the enumeration of the new custom field
* The field on a work item listing your resources by title
* The picked resource shown on the work item after saving

## See Also

* [Enumeration Properties](/gantt/reference/configuration/enumeration-properties.md) — every property named on this page
* [Resource Breakdown Structure](/gantt/concepts/resource-breakdown-structure.md) — the enumeration next to the hierarchical picker
* [Set Up a Hierarchical Resource Picker](/gantt/guides/resources/hierarchical-resource-picker.md)
* [Configure Resource Fields](/gantt/guides/resources/resource-field-configuration.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.