---
sourceDocument: Australia Sales and Order Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Sales and Order Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Table-based picklists

# Table-based picklists {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

A table-based picklist lets an administrator query and retrieve data from managed tables.

Table-based picklists allow administrators to retrieve configuration picklist field options from a managed table. This feature is particularly useful when:

* The number of options in the picklist is large. The buyside UI representation of the table- based picklist paginates options, and thus, improves the userʼs experience of page response.
* Several picklists make use of the same options. Picklist-specific query filters facilitate data reuse.

{#table-based_picklists__ul_kpv_gkq_2hc}

Managed Tables are not deployed. As a result, a picklist which references table data for its options will present the end-user with the data available in the table when it is queried, at runtime.

If the referenced managed table contains duplicate data, the application attempts to present the best picklist experience to the user at runtime. For example, consider the following three scenarios.

Scenario 1:
{#table-based_picklists__entry__2}

| Label | Value |
|-|-|
| Apple | apple |
| Banana | banana |
| Banana | banana |
| Chayote | chayote |
[Tabelle : 1. Two identical items]

CPQ removes the second instance of Banana \[banana\], presenting the user with three picklist options.

Scenario 2:
{#table-based_picklists__entry__12}

| Label | Value |
|-|-|
| Apple | apple |
| Banana | banana |
| Banana | banana2 |
| Chayote | chayote |
[Tabelle : 2. Two items with the same label but different values]

In this scenario, CPQ retrieves picklist options with four unique values. Unfortunately, two values, "banana" and "banana2" share the same label, "Banana". The app cannot determine which value is best for label, "Banana".
Therefore, the user will be presented with a total of four options, two labeled "Banana". Administrators must mind their managed tables data to avoid this poor end-user experience.

Scenario 3:
{#table-based_picklists__entry__22}

| Label | Value |
|-|-|
| Apple | apple |
| Banana | banana |
| Banana2 | banana |
| Chayote | chayote |
[Tabelle : 3. Two items with different labels but identical values]

When duplicate values are returned from a managed table, CPQ displays the label associated with the first occurrence of the value. All other labels associated with that value are eliminated and are not displayed as picklist options
to the end-user.

If the referenced table returns a row with no data contained in the label or value, the application will ignore the entry, and the record will not be presented to the end-user as a picklist option.  
Hinweis:  
Table-based picklists do not support picklist extensions.
**Zugehörige Konzepte**   

* [Picklists and picklist extensions in rules](https://servicenow-prod.fluidtopics.net/F4sqWch008LgaXeWalKAOg "Learn how to use picklist extensions (PLEs) effectively in rules. Understand how filtering, inclusion, and exclusion interact, and apply correct operators like equals and contains for single- and multi-select picklists to ensure accurate rule behavior in advanced configurations.")