Example: Deleting catalog filter condition groups
You can delete your catalog filter condition groups by using the Data Load utility. These examples use a CSV file to demonstrate how to delete your catalog filter condition group data.
This example uses a CSV file to demonstrate how to insert, replace, or delete your data. You can also create and use an XML formatted file to insert, replace, or delete your data. If you choose to create and use an XML formatted file, ensure that your XML elements use the same names as are used for CSV column names.
CSV file with sample catalog filter condition group data
CatalogFilterConditionGroup.csv
The file contains sample catalog filter condition group data. Each column is delimited by a comma.
CatalogFilterName | StoreIdentifier | CatalogIdentifier | CatalogGroupIdentifier | ConditionGroupIdentifier | ConditionRelation |
---|---|---|---|---|---|
CatalogFilterA | Madisons | Madisons | Lounge Chairs | conditionLoungeChairAnd | And |
CatalogFilterA | Madisons | Madisons | Lounge Chairs | conditionLoungeChairOr | Or |
CSV column and XML element definitions
- CatalogFilterName
- Required, String: The name of the catalog filter. Ensure that the combination of CatalogIdentifier, StoreIdentifier, and CatalogFilterName are unique.
- StoreIdentifier
- Required, String: The identifier of the store that the catalog filter belongs to.
- CatalogIdentifier
- Required, String: The identifier of the catalog that the catalog filter belongs to.
- CatalogGroupIdentifier
- Required, String: The identifier of the catalog group to include or exclude in this catalog filter.
- ConditionGroupIdentifier
- Required, String: The unique name of the condition.
- ConditionRelation
- Required, String: The relationship for the condition: Or, And.
- CatalogFilterId
- Optional, String: The reference number of the catalog filter. If the reference number is provided in the CSV, then it is used. If this field is provided, then the CatalogFilterName, CatalogFilterName, CatalogIdentifier is not needed.
Business context data
The following code snippet from the wc-dataload-env.xml configuration file provides the required business context data:
<_config:BusinessContext storeIdentifier="Deprecated featureMadisons" catalogIdentifier="Madisons">
</_config:BusinessContext>
- storeIdentifier
- String: The store identifier, for example "Deprecated featureMadisons". This parameter is used when the storeIdentifier is not provided in the CSV file. If the storeIdentifier is provided in the CSV file, it is used. The storeIdentifier is used to retrieve the storeID and the ownerID.
- catalogIdentifier
- String: The catalog identifier, for example "Madisons". This parameter is used when the catalog identifier is not provided in the CSV file. If the catalogIdentifier is provided in the CSV file, it is used.
Mapping data
The following snippet from the sample configuration file demonstrates how to map each column of data in the source CSV file to a value.
<_config:DataReader className="com.ibm.commerce.foundation.dataload.datareader.CSVReader" firstLineIsHeader="true" useHeaderAsColumnName="true" />
The following snippet from the sample configuration file demonstrates how to map each column of the data in the CSV file to a business object logical schema path. The attribute 'value' represents the name of a column of the CSV file that is defined in the configuration snippet above. Each column in the CSV file must have a mapping to the logical schema path. If the optional fields specified above are present in the CSV file, the mapping for them must be added. The mapping logical schema path is specified in the following table.
<_config:DataMapping>
<_config:mapping xpath="CatalogFilterIdentifier/UniqueID" value="CatalogFilterId" />
<_config:mapping xpath="CatalogFilterIdentifier/ExternalIdentifier/Identifier" value="CatalogFilterName" />
<_config:mapping xpath="CatalogFilterIdentifier/ExternalIdentifier/StoreIdentifier/ExternalIdentifier/NameIdentifier" value="StoreIdentifier" />
<_config:mapping xpath="CatalogFilterIdentifier/ExternalIdentifier/CatalogIdentifier/ExternalIdentifier/Identifier" value="CatalogIdentifier" />
<_config:mapping xpath="CatalogGroupSelection/CatalogGroupSelectionIdentifier/ExternalIdentifier/CatalogGroupIdentifier/ExternalIdentifier/GroupIdentifier" value="CatalogGroupIdentifier" />
<_config:mapping xpath="CatalogGroupSelection/ConditionGroup/ConditionGroupIdentifier/ExternalIdentifier/Identifier" value="ConditionGroupIdentifier" />
<_config:mapping xpath="CatalogGroupSelection/ConditionGroup/conditionRelation" value="ConditionRelation" />
<_config:mapping xpath="CatalogGroupSelection/ConditionGroup/UserData/UserDataField[0]/Field1" value="Field1" />
<_config:mapping xpath="CatalogGroupSelection/ConditionGroup/UserData/UserDataField[0]/Field2" value="Field2" />
<_config:mapping xpath="CatalogGroupSelection/ConditionGroup/UserData/UserDataField[0]/Field3" value="Field3" />
<_config:mapping xpath="CatalogGroupSelection/ConditionGroup/UserData/UserDataField[0]/Field4" value="Field4" />
<_config:mapping xpath="CatalogGroupSelection/ConditionGroup/UserData/UserDataField[0]/Field5" value="Field5" />
<_config:mapping xpath="" value="Delete" deleteValue="1"/>
</_config:DataMapping>
Sample
XML fileBusiness object mediator
The mediator class name is com.ibm.commerce.catalogfilter.dataload.mediator.CatalogFilterConditionGroupMediator. The corresponding logical schema is CatalogFilter.xsd.