---
schema_version: "1"
id: bdb6841b36d1d185e23f9d385fdceb6a840c633676dc6a5d86466ef18c883e84
title: Create Feature Parameters for Your Second-Generation Managed Package
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform-pkg-exchange/managed_packaging/guides/second-generation/sfdx-fma/sfdx-dev-dev2gp-fma-create-feature-parameters.md
canonical_url: https://developer.salesforce.com/docs/platform/pkg2-dev/guide/sfdx-dev-dev2gp-fma-create-feature-parameters.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 25c3db1a63d0a904f788888f42619bb7bd4701d318deeccc09594da4ffb1120f
products:
  - Second-Generation Managed Packaging Developer Guide
  - merged-docs
---

# Create Feature Parameters for Your Second-Generation Managed Package

To create a feature parameter for a 2GP managed package, create an individual XML file. Here are details on the file naming convention, folder structure, and the attributes you use when creating feature parameters.

**note:** Feature parameters for managed 1GP packages are created in the packaging org’s UI, see [Create Feature Parameters in Your Packaging Org](https://developer.salesforce.com/docs/atlas.en-us.pkg1_dev.meta/pkg1_dev/fma_create_feature_parameters.htm) in the _First-Generation Managed Packaging Developer Guide_ for details.

A package can include up to 200 feature parameters.

## Folder Structure

Feature parameters are stored as files in your Salesforce DX project folder.

Under the root force-app folder, create a folder and name it featureParameters. Store your feature parameter files in the feature parameters folder. Each feature parameter you create must have its own separate file.

**note:** It’s not possible to create feature parameters using a scratch org’s user interface.

## File Naming Convention

The naming format for feature parameter files is `<name>.featureParameter<type>-meta.xml`.

The name is the API name of the feature parameter.

The type is the feature parameter type. Feature parameters can be booleans, integers, or dates.

| Type    | File Name Format                    |
| ------- | ----------------------------------- |
| Boolean | `.featureParameterBoolean-meta.xml` |
| Date    | `.featureParameterDate-meta.xml`    |
| Integer | `.featureParameterInteger-meta.xml` |

## Feature Parameter Attributes

Feature parameters include these three fields.

| Field Name        | Description                                                                                                                                                                                                                                         |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| dataflowDirection | Indicates which direction this parameter is transferring data. Each feature parameter value gets transferred in one of two directions: from your LMO to a subscriber org (LmoToSubscriber), or from a subscriber org to your LMO (SubscriberToLmo). |
| masterLabel       | The label of the feature parameter. This label displays in the app.                                                                                                                                                                                 |
| value             | The value of the feature parameter. Booleans, integers, and dates are all valid values. Integer values can’t exceed nine digits.                                                                                                                    |

**note:** After a feature parameter is included and released in the package version, the data flow direction can’t be changed.

## Examples of Feature Parameter file

**AdvancedPricingEnabled.featureParameterBoolean-meta.xml**

```nolang
<FeatureParameterBoolean xmlns="http://soap.sforce.com/2006/04/metadata">
      <dataflowDirection>SubscriberToLmo</dataflowDirection>
      <masterLabel>Advanced Pricing Enabled</masterLabel>
      <value>true</value>
  </FeatureParameterBoolean>

```

**NumberofLedgers.featureParameterInteger-meta.xml**

```nolang
<?xml version="1.0" encoding="UTF-8"?>
  <FeatureParameterInteger xmlns="http://soap.sforce.com/2006/04/metadata">
      <dataflowDirection>SubscriberToLmo</dataflowDirection>
      <masterLabel>Number of Ledgers</masterLabel>
      <value>7</value>
  </FeatureParameterInteger>

```

**ProjectActivationDate.featureParameterDate-meta.xml**

```nolang
<?xml version="1.0" encoding="UTF-8"?>
  <FeatureParameterDate xmlns="http://soap.sforce.com/2006/04/metadata">
      <dataflowDirection>LmoToSubscriber</dataflowDirection>
      <masterLabel>Date of Activation of the Project</masterLabel>
      <value>2020-01-25</value>
  </FeatureParameterDate>

```