CatalogEntryAssociation

Use the CatalogEntryAssociation keyword to load merchandising associations between catalog entries.

Previously, you could load this data only in CSV formatted files. You can now load information in a CSV or XML formatted input file. Your input file must contain CSV column or XML element names and definitions that specify the characteristics of the business object type you are loading into your database.

CSV column and XML element definitions

PartNumber: (String) The part number of the source catalog entry in the association. Either this field or the CatalogEntryUniqueId is required. The part number for a catalog entry displays in Management Center as the value for the catalog entry Code property.
CatalogEntryUniqueId: (Integer) The internal unique reference number of the catalog entry. Either this field or the PartNumber is required.
AssociationType: (String) The type of merchandising association you want to use. The available values are CrossSell, UpSell, Accessory,, and Replacement. This field cannot be null.
TargetPartNumber: (String) The part number of the target catalog entry in the association. Either this field or the TargetCatalogEntryUniqueId is required.
TargetCatalogEntryUniqueId: The internal unique reference number of the target catalog entry. Either this field or the TargetPartNumber is required.
TargetStoreIdentifier: (String) The identifier of the store that owns the target catalog entry. Use this field when your site uses the extended sites model, where the store that owns the target catalog entry is different from the store that owns the source catalog entry.
TargetStoreUniqueId: (Integer) The unique reference number of the store that owns the target catalog entry. Use this field when your site uses the extended sites model, where the store that owns the target catalog entry is different from the store that owns the source catalog entry.
Sequence: (Decimal) A number that is used to control the order in which the target catalog entries (merchandising associations) display on the storefront. For example, for a dress that targets a purse and shoes, you can assign 1 to the purse and 2 to the shoes. This number can include decimal places, for example, 1.1.
SemanticSpecifier: (String) The semantic specifier of the merchandising association. Examples of semantic specifiers are "REQUIRES", "NONE", "TEMP", or "COMES_WITH". If no value is provided, then the default value is set to "NONE".
Quantity: (Decimal) The quantity of target catalog entries required. For example, if the source catalog entry is a camera, and the target catalog entry is battery type that it uses, the quantity indicates the number of batteries required.
Field1: (String) A user-defined field available for merchandising association customization purposes.
Field2: (Integer) A user-defined field available for merchandising association customization purposes.
Field3: (Decimal) A user-defined field available for merchandising association customization purposes.
Date1: (Timestamp) A user-defined field available for merchandising association customization purposes.
Delete: (String) A flag that indicates whether to delete. Specify 1 to delete the row.