---
schema_version: "1"
id: c8824f003d1f93b3ddc585280e44075bb7c2a249c2b515ebf75b8aae32ef8efc
title: Controlling Field Property (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_controlling_field_property_1.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_controlling_field_property_1.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 72670814da76a757a859fd003ac6c65e90c7abcbafdc07edf2a5fd29cf3c33a2
description: For the managed package runtime, the Controlling Field Property on a Select Element can display Select Field Values based on the selection of another value from a Controlling Select field.
products:
  - Omnistudio
release: "264"
---
# Controlling Field Property (Managed Package)

For the managed package runtime, the Controlling Field Property on a Select Element can display Select Field Values based on the selection of another value from a Controlling Select field.

![Managed Package app icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US).

Both the controlling and dependent fields must pull their field values from a field in Salesforce using the sObject property and those fields must have a Field Dependency setup between one another via Salesforce Field Dependency feature.

**Example Controlling Field Setup**

![Example controlling field setup](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/omnistudio_for_managed_packages/images/salesforce_omniscript_controllingfieldsetup.png)

**Controlling Field Configuration**

![Controlling field configuration](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/omnistudio_for_managed_packages/images/salesforce_omniscript_controllingfieldconfiguration.png)

**Dependent Field Configuration**

![Dependent field configuration](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/omnistudio_for_managed_packages/images/salesforce_omniscript_dependentfieldconfiguration.png)

**Defined Field Dependency in Salesforce**

![Defined field dependency in Salesforce](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/omnistudio_for_managed_packages/images/salesforce_omniscript_definedfielddependency.png)

## Using Option Source Custom

When using Custom as an option source, you can define an Apex class that will pull in the Picklist values source. See [Populating Picklist Values From Apex (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_populating_picklist_values_from_apex.htm&release=264.0.0&type=5 "For the managed package runtime, you can populate Select, Multi-select, and Radio elements from an Apex class that implements Callable and Vlocity Open Interface. The values for the element are obtained during the Omniscript's activation.").

#### See Also

- [Dependent Picklists](https://help.salesforce.com/s/articleView?id=platform.fields_about_dependent_fields.htm&type=5&language=en_US)