Skip to content

Commit b1e16b5

Browse files
authored
Merge pull request #11233 from MicrosoftDocs/matp-437053
Matp 437053
2 parents cfae0f7 + 668173c commit b1e16b5

File tree

1 file changed

+13
-41
lines changed

1 file changed

+13
-41
lines changed

powerapps-docs/maker/data-platform/custom-picklists.md

Lines changed: 13 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Step-by-step instructions for how to create a choice in Power Apps.
44
author: lancedMicrosoft
55
ms.component: cds
66
ms.topic: how-to
7-
ms.date: 05/07/2025
7+
ms.date: 06/02/2025
88
ms.subservice: dataverse-maker
99
ms.author: lanced
1010
search.audienceType:
@@ -24,18 +24,19 @@ Choices are either global or local. You can define a choice to use a set of opti
2424

2525
## Create a global choice within a solution
2626

27-
1. Sign into [powerapps.com](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc), select **Solutions**, and then open the solution you want. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
27+
1. Sign into [powerapps.com](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc) select **Solutions**, and then open the solution you want. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
2828
1. On the command bar, select **New** > **Choice**.
2929
1. Enter the following properties:
30-
- **Display name**. Enter the **Display name** for your column. The **Display name** is used when presenting this column to your users.
30+
- **Display name**. Enter the **Display name** for your column. The **Display name** is used when presenting this column to your users.
3131
- In the **Label** field, enter the label you want displayed for the choice option.
3232
- The **Value** number represents a unique value for the option and isn't displayed in the choice column in an app. Notice there's a number generated for each **Value** automatically. We recommend that you not change this. Having a unique **Value** helps ensure that the value will be different from other option values that might be defined in other solutions and imported into your environment.
3333
- Select the color picker to the left of the **Label** if you want a color to appear for the option in model-driven app charts.
3434
- **Additional properties**.
3535
- **Description**. Add a description for the option.
3636
- **External value**. This value is used for virtual tables to map a value in an external data source with this option.
37-
- **Hidden**. Hide the option from the choice column at runtime in apps.
38-
37+
- **Hidden**. Hide the option from the choice column at runtime in apps. For more information about the limitations of this property, go to [Choice hidden property limitations](#choice-hidden-property-limitations).
38+
> [!CAUTION]
39+
> The Hidden property should never be used as a secure way to prevent users from viewing or editing column values. These properties only apply to app components such as model-driven app forms and views but don't have an effect on a user's data privileges. When a column is hidden, users can still access column data in other ways, such as by making Web API calls. To secure columns, use [column-level security to control access](/power-platform/admin/field-level-security).
3940
1. Select **New choice** to create another option for the choice.
4041
1. Repeat the previous step to until you have the options you want for the choice.
4142
1. Expand **Advanced options** to display additional properties:
@@ -51,15 +52,15 @@ Choices are either global or local. You can define a choice to use a set of opti
5152

5253
Create a local choice column for a table that can be used in forms and views within a solution.
5354

54-
1. Sign into [powerapps.com](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc), select **Solutions**, and then open the solution you want. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
55+
1. Sign into [powerapps.com](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc) select **Solutions**, and then open the solution you want. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
5556

5657
1. Open the table where you want to create the local choice, and then on the command bar, select **New** > **Choice**.
5758

5859
1. In the **New column** panel, enter properties for the choice column.
5960

6061
### Configure properties for a local choice
6162

62-
- **Display name**. Enter the **Display name** for your column. The **Display name** is used when presenting this column to your users.
63+
- **Display name**. Enter the **Display name** for your column. The **Display name** is used when presenting this column to your users.
6364
- **Description**. Enter an optional description of the choice column.
6465
- **Data type**. Select **Choice** > **Choice**. Select **Choice** > **Yes/No** if you want a two option single select choice field.
6566
- **Behavior**. Select calculated to enable the column to be included in calculated columns to automate manual calculations.
@@ -88,42 +89,13 @@ Now the local choice column appears in the form and view designers to add for th
8889
## Create and edit global choices using solution explorer
8990

9091
For information about how to create and edit global choices using the classic solution explorer, go to [Create or edit a global option set (on-premises)](/dynamics365/customerengagement/on-premises/customize/create-edit-global-option-sets).
91-
<!-- Solution explorer provides one way to create and edit global choices for Dataverse.
92-
93-
> [!NOTE]
94-
> [make.powerapps.com](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc) is the best way to create and edit choice columns.
95-
96-
### Open solution explorer
97-
98-
Part of the name of any global choice you create is the customization prefix. This is set based on the solution publisher for the solution you’re working in. If you care about the customization prefix, make sure that you are working in an unmanaged solution where the customization prefix is the one you want for this global choice . More information: [Change the solution publisher prefix](create-solution.md#solution-publisher)
99-
100-
[!INCLUDE [cc_navigate-solution-from-powerapps-portal](../../includes/cc_navigate-solution-from-powerapps-portal.md)]
101-
102-
### View global choices
103-
104-
With solution explorer open, under **Components** select **Option Sets**.
105-
106-
![View global choices.](media/view-global-option-sets-solution-explorer.png)
107-
108-
> [!NOTE]
109-
> Some system global choices are not customizable. These options may change with updates or new versions so we recommend you don’t use them unless you are certain that your requirements align with the way that Dataverse uses these values.
110-
111-
### Create a global choice
112-
113-
> [!NOTE]
114-
> You do not need to create a global choice before you use it within a custom column. When you create a new choice column you have the option to create a new global choice or use an existing one. See [Choice column options](create-edit-field-solution-explorer.md#choice-column-options)
115-
116-
While viewing global choices, click **New** to open a form to define the global choice .
117-
118-
![Create global choice .](media/create-global-option-set-solution-explorer.png)
119-
120-
Type a **Display name** that will be visible to people with the system administrator or customizer role who will choose this global choice when defining new columns that use it. This name will not be visible to people using your apps.
12192

122-
A **Name** column value will be generated for you based on the **Display name** you enter. It will include the customization prefix for the Solution publisher in the context of the solution you are working in. You can change the generated portion of the **Name** column value before you save.
93+
## Choice hidden property limitations
12394

124-
Type a **Description** for the global choice .
95+
- The choice column hidden property is only applicable for model-driven apps. Other components that use Microsoft Dataverse tables, such as canvas apps, don't use the choice column hidden property.
96+
- The choice column hidden property only works for app with the [modern, refreshed look for model-driven apps enabled](../../user/modern-fluent-design.md).
97+
- The choice column hidden property isn't currently supported for multi-select choices even when the **Selecting multiple choices is allowed** option is selected.
98+
- The hidden property *only hides the option label and value when displayed in a model-driven app*. Even when hidden, choice labels and values can be viewed and set by accessing the Dataverse table directly, such as from make.powerapps.com. Hidden options can also be set using the [`setValue` client API method](../../developer/model-driven-apps/clientapi/reference/attributes/setValue.md).
12599

126-
> [!TIP]
127-
> Use the **Description** to explain the purpose of this global choice . This value is not visible to users of the application, it is for other people with the system administrator or customizer role who may want to know why this particular global choice was created. -->
128100

129101
[!INCLUDE[footer-include](../../includes/footer-banner.md)]

0 commit comments

Comments
 (0)