> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/ecma2-framework/v2.0/advanced/index/lithnet.ecma2framework.dropdownparameterattribute.md).

# DropdownParameterAttribute

Namespace: Lithnet.Ecma2Framework

Defines a configuration parameter that is rendered as a drop down control in the management agent's configuration pages

```csharp
public class DropdownParameterAttribute : DataParameterAttribute
```

Inheritance [Object](https://docs.microsoft.com/en-us/dotnet/api/system.object) → [Attribute](https://docs.microsoft.com/en-us/dotnet/api/system.attribute) → [ParameterAttribute](/ecma2-framework/v2.0/advanced/index/lithnet.ecma2framework.parameterattribute.md) → [DataParameterAttribute](/ecma2-framework/v2.0/advanced/index/lithnet.ecma2framework.dataparameterattribute.md) → [DropdownParameterAttribute](/ecma2-framework/v2.0/advanced/index/lithnet.ecma2framework.dropdownparameterattribute.md)

## Properties

### **Extensible**

Gets a boolean value that indicates if users should be able to specify their own value in addition to the displayed values

```csharp
public bool Extensible { get; }
```

#### Property Value

[Boolean](https://docs.microsoft.com/en-us/dotnet/api/system.boolean)<br>

### **DisplayedValues**

Gets the list of values that should be displayed in the drop down list

```csharp
public String[] DisplayedValues { get; }
```

#### Property Value

[String\[\]](https://docs.microsoft.com/en-us/dotnet/api/system.string)<br>

### **Name**

Gets the name of the parameter, as shown to the user on the MIM configuration page

```csharp
public string Name { get; }
```

#### Property Value

[String](https://docs.microsoft.com/en-us/dotnet/api/system.string)<br>

### **TypeId**

```csharp
public object TypeId { get; }
```

#### Property Value

[Object](https://docs.microsoft.com/en-us/dotnet/api/system.object)<br>

## Constructors

### **DropdownParameterAttribute(String, Boolean, String\[])**

Initializes a new instance of the DropdownParameterAttribute class

```csharp
public DropdownParameterAttribute(string name, bool extensible, String[] displayedValues)
```

#### Parameters

`name` [String](https://docs.microsoft.com/en-us/dotnet/api/system.string)\
The name of the parameter, as shown to the user on the MIM configuration page

`extensible` [Boolean](https://docs.microsoft.com/en-us/dotnet/api/system.boolean)\
A boolean value that indicates if users should be able to specify their own value in addition to the displayed values

`displayedValues` [String\[\]](https://docs.microsoft.com/en-us/dotnet/api/system.string)\
The list of values that should be displayed in the drop down list


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lithnet.io/ecma2-framework/v2.0/advanced/index/lithnet.ecma2framework.dropdownparameterattribute.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
