> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/appendix/miscellaneous/picklists.md).

# PickLists

## Using PickLists

appRules includes activities for managing data source picklists (option sets).

The activities are in the appConnector.List module (see [Base Activities](/apprules-r-documentation/platform/platform-features/base-activities/base-activities-1.md) User Guide):

\- LookupPickListRecord

\- IsPickListValueValid

PickLists can be entered manually or generated automatically when data source metadata is created.  For example, when a Microsoft Dynamics CRM or Salesforce data sources are created, the system automatically creates the picklists for all entities.

![](/files/-MFzEUlbri-x1fH_ntHL)

When a picklist entry is defined, you can also enter alternate values associated with the entry.  This feature can be used for looking up values for picklist entries.  In the example below, when the Account.customertypecode entry is loaded, the three alternate values associated with it are also loaded and can be used any where in your project.

![](/files/-MFzEUlcQc3Jh6xLD2UU)

## LookupPickListRecord Activity

The LookupPickListRecord activity which is part of the module, allows you to load the values of a picklist into a record.  The record values (key/description) can then be used in the running project just like other values (using “DataFieldValue” source value).

## IsPickListValid Activity

The IsPickListValid activity which is part of the appConnector.List module, checks whether a value belongs to a picklist.   The value can be the key or description of the picklist.   The activity returns True or False and can be directly tested using the ActivityResult condition type.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.appstrategy.com/apprules-r-documentation/appendix/miscellaneous/picklists.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.