Multiple pricing units in migration datasets

note

Before migrating datasets to your marketplace, contact your AppDirect technical representative.

Marketplace Managers can include subscriptions with multiple pricing units using the Company Entitlements migration file data on the migration creation page. They can add subscriptions with multiple pricing units using one of the following methods:

• Add a new column as a JSON field for each edition pricing UUID to the Company Entitlements file.
• Add new columns with a specific format for each edition pricing UUID.

To add a new column as a JSON field for each edition pricing UUID to the Company Entitlements file

The format of the JSON field is as follows:

[
 {
   "PRICING_UNIT": <value of the pricing unit; Required if EDITION_PRICING_UUID is provided>,
   "CHANNEL_SKU": <value of the channel sku; Required if EDITION_PRICING_UUID
is not provided.>,
   "UNITS": <value of the unit; Required>,
   "HISTORICAL_PRICE": <associated value; Optional (required as per the use case of the migration>,
   "RESELLER_MARKUP_PRICE": <associated value; Optional (required as per the
use case of the migration>,
   "CHANNEL_MARKUP_PRICE": <associated value; Optional (required as per the use case of the migration>,
   "WHOLESALE_MARKUP_PRICE": <associated value; Optional (required as per the
use case of the migration>
   },
  {
<Number of blocks required>
  }
]

Add new columns with a specific format for each edition pricing UUID

For an edition pricing UUID (EDITION_PRICING_UUID), the Pricing Details corresponding to each pricing unit, is provided in the Company Entitlement file with new columns that have the following format:

PRICINGDETAILS:<Index Number>:<Attribute Name>

Where:

• PRICINGDETAILS is the block identifier.
• Index number is a numeric value that is constant across the block and should start at 1.
• Attribute name is the entity identifier.

For example PRICINGDETAILS:1:PRICING_UNIT

The following table describes the attributes in the pricing details block. Each pricing details block can be repeated. The index number defines each pricing block, so it should be the same across each block.

Attribute name	Description	Header	Mandatory
UNITS	The number of pricing units in the order.	PRICINGDETAILS:<IndexNumber>:UNITS	Yes
PRICING_UNIT	The unit description of the edition.	PRICINGDETAILS:<IndexNumber>:PRICING_UNIT	Yes, if the EDITION_PRICING_UUID is provided.
CHANNEL_SKU	This maps to the product identifier defined for every pricing of the application that is published.	PRICINGDETAILS:<Index Number>:CHANNEL_SKU	Yes, if the EDITION_PRICING_UUID is not provided.
HISTORICAL_PRICE	Historical price of the subscription used to lock prices for auto-renewal contracts.	PRICINGDETAILS:<IndexNumber>:HISTORICAL_PRICE	No
RESELLER_MARKUP_PRICE	The reseller price of the product. It is a markup that is applied on the base item price.	PRICINGDETAILS:<IndexNumber>:RESELLER_MARKUP_PRICE	No
CHANNEL_MARKUP_PRICE	The channel markup price of the product.	PRICINGDETAILS:<IndexNumber>:CHANNEL_MARKUP_PRICE	No
WHOLESALE_MARKUP_PRICE	The wholesale price of the product.	PRICINGDETAILS:<IndexNumber>:WHOLESALE_MARKUP_PRICE	No

If you choose either of the procedures above to migrate multiple pricing units, the following existing columns are not required in the Company Entitlement file:

• UNITS
• PRICING_UNIT
• CHANNEL_SKU
• HISTORICAL_PRICE
• RESELLER_MARKUP_PRICE
• CHANNEL_MARKUP_PRICE
• WHOLESALE_MARKUP_PRICE