On the Advance SKU Search page, there are 2 tabs Build a Condition and Saved Conditions. The Build a Condition tab is selected, by default. Here, you will build the conditions to search the required SKU data. Once the catalog is selected, you need to add a category condition, that is, build conditions using the categories available.
To view the various categories available, click Add. The following is displayed.
There are 5 categories available to build the search filters and each of these can be used individually or in a combination to build the required filters. Each of these categories have different options which help in building the required condition. Following are the options:
Label – The category selected will be the label. If an attribute is selected, it is being used as a label to build the condition.
Operator – This consists of numeric and string operators such as equals, starts with, contains, is greater than and so on. The operators will change based on the label selected.
Predicate – The value entered for the label selected based on which the operator will be applied, and the data will be filtered.
Multiple complex conditions can be built using the AND/OR conjunctions. These conjunctions can be used between every option selected.
Let us look at each of the categories and the various options available.
Attribute
You can build a condition using the attribute name. Select the category as Attribute and the following is displayed.
The Search by Attribute Name option is selected, by default. You can start typing the name of the attribute and a drop-down list of all matches is displayed.
You need to select the attribute name on which the condition is to be built. If you select Search by Attribute Group, only those attributes present in the attribute group for the selected catalog will be available for selection as shown below.
Here, the operator is Equals which means that the name of the attribute should be the exact match for the condition being built. Once the attribute name is selected, you can add additional attribute specific conditions.
Click the Add Attribute Condition Element 
icon and the following appears.
There are 2 conditions available for attributes:
Attribute Value – You can type the attribute value based on which the data will be filtered. The following operators can be applied for the attribute value:
Contains
Does Not Contain
Does Not End With
Does Not Equal
Does Not Equal Any Of
Does Not Start With
Ends With
Equals
Equals Any Of
Has Multiple Values
Has Single Value
Is Greater Than
Is Greater Than Or Equal To
Is Less Than
Is Less Than Or Equal To
Starts With
For example, let us search for SKUs having an attribute as Dial Color and which does not have Black as the value. In this case, select the attribute as Dial Color. Select the condition as Attribute Value, Operator as Does Not Contain and type the value as Black as shown below.
Thus, when you search, all SKUs having an attribute Dial Color and value other than Black will be displayed.
Validation Failure – Here, you can filter attributes based on whether the attribute selected has validation error or not. The following operators can be applied:
Does Not Exist – This option will display a list of all SKUs having the selected attribute without any validation error.
Exists – This option will display a list of all SKUs having the selected attribute with a validation error.
You can add multiple attribute conditions for an attribute selected by clicking the 
icon and a combination of all will be considered when the search is executed. Also, you can click the Remove Attribute Condition Element 
icon next to the attribute condition to remove it any time, if not relevant.
Similarly, you can also add an entire attribute structure by clicking Add > Condition Category > Attribute and build conditions with multiple attributes as shown below.
NOTE | You can also add a different category along with attributes and build conditions using 2 different categories or multiple categories, as required. For example, click Add > Condition Category > SKU and now you can build conditions using attributes and SKUs as shown below. |
Details on how to build a condition to search SKUs is explained here.
Digital Asset
You can build a condition using the various digital asset parameters. There are multiple categories available for assets based on which conditions can be built. Select the category as Digital Asset and the following is displayed.
The following table provides an overview of the various digital asset categories, the operators applicable and the values to be entered.
Table 17: Digital Asset Conditions
Query Category | Operators | Values | Comments |
|---|---|---|---|
Digital Asset Effective Begin Date | The following operators are available for this category:
| There is an option to select the relevant date from the calendar | Based on the date and operator selected, the data will be filtered. |
Digital Asset Effective End Date | The same operators as mentioned for Effective Begin Date are available. | Same as above | Same as above |
Digital Asset Importance | The following operators are available for this category:
| None | This option will filter assets based on whether they are marked as primary asset or not. If Is Primary is selected as the operator, all SKUs having assets marked as primary will be displayed. |
Digital Asset Linkage | The following operators are available for this category:
| None | This option will filter all SKUs that have assets linked to it. |
Digital Asset Name | The following operators are available for this category:
| Based on the operator selected, you need to enter the value. | For example, let us search for SKUs having assets with the name watch. In this case, select the Operator as Contains and type the value as watch. All SKUs having asset names containing the word watch will be displayed. |
Digital Asset Type | The following operators are available for this category:
| The following asset types can be selected:
| In this case, if the Operator is selected as Equals and asset type as Videos, only those SKUs which have videos linked to it will be displayed. |
Digital Asset User Uploaded File Name | The same operators as mentioned for Digital Asset Name are available. | Based on the operator selected, you need to enter the value. | The user uploaded file name is basically the same value for all assets except for assets uploaded as URLs. In case of URLs, the user uploaded file name will be the link. |
Once the asset query is selected, you can add additional asset conditions.
Click the Add Digital Asset Condition Element 
icon and the following appears.
The options available for building additional conditions are the same as mentioned in Table 17: Digital Asset .
For example, let us search for SKUs having asset name Watch and which is used as primary assets. In this case, select the category as Digital Asset Name, with operator Contains and value as Watch. For the second condition, select the category as Digital Asset Importance with operator as Is Primary as shown below.
Thus, when you search, all SKUs having an asset name as watch and which are also marked as primary asset will be displayed. Here, if a SKU has asset name as watch but if it is not marked as primary, it will not be displayed in the list. It is important that both the conditions are met as the conjunction AND is used here.
You can add multiple digital asset conditions by clicking the 
icon and a combination of all will be considered when the search is executed. Also, you can click the Remove Digital Asset Condition Element 
icon next to the condition to remove it any time, if not relevant.
NOTE | You can also add a different category (attribute / assets / taxonomy) along with assets and build conditions using 2 different categories or multiple categories, as required. |
Details on how to build a condition to search SKUs is explained here.
SKU
You can build a condition using the various SKU parameters. There are multiple categories available for SKUs based on which conditions can be built. Select the category as SKU and the following is displayed.
The following table provides an overview of the various SKU categories, the operators applicable and the values to be entered.
Query Category | Operators | Values | Comments |
|---|---|---|---|
SKU Item Id | The following operators are available for this category:
| Based on the operator selected, you need to enter the value. | For example, let us search for SKUs starting with series 100, as these SKUs need to be edited. In this case, select the Operator as Starts With and type the value as 100. All SKUs starting with series 100 will be displayed. |
SKU Title | The same operators as mentioned for SKU Item Id are available along with the following additional operators:
| Same as above | Here too, based on the value entered and the operator selected, the data will be filtered accordingly. |
SKU Type | The following operator is available for this category:
| SKU and Product Family are the 2 types of SKUs available. By default, both are selected which means that any condition applied will check for matches in both SKUs and PF. | You can select any type or both based on the search. For example, if we need to search PFs specifically, the SKU option can be deselected and any condition applied will display matches w.r.t to PFs only. |
Once the SKU query is selected, you can add additional SKU conditions.
Click the Add SKU Condition Element 
icon and the following appears.
The options available for building additional conditions are the same as mentioned in Table 18: SKU Conditions.
For example, we need to search for SKUs which do not contain the series 100 in the Item Id and should only be SKUs and not PFs. In this case, select the category as SKU Item Id, with operator Does Not Contain and value as 100. For the second condition, select the category as SKU Type with operator as Equals Any of and deselect PF as we only need SKUs as shown below.
Thus, when you search, only SKUs which do not contain 100 in the Item Id will be displayed. Here, even if a PF Id exists matching the criteria, it will not be displayed in the list as it is deselected. It is important that both the conditions are met as the conjunction AND is used here.
You can add multiple SKU conditions by clicking the 
icon and a combination of all will be considered when the search is executed. Also, you can click the Remove SKU Condition Element 
icon next to the condition to remove it any time, if not relevant.
NOTE | You can also add a different category (attribute / assets / taxonomy) along with SKUs and build conditions using 2 different categories or multiple categories, as required. |
Details on how to build a condition to search SKUs is explained here.
Taxonomy
You can build a condition using the various Taxonomy parameters. There are multiple categories available for taxonomy based on which conditions can be built. Select the category as Taxonomy and the following is displayed.
The following table provides an overview of the various taxonomy categories, the operators applicable and the values to be entered.
Query Category | Operators | Values | Comments |
|---|---|---|---|
Catalog Hierarchy Name | The following operators are available for this category:
| Based on the operator selected, you need to enter the value. | This filters data based on the hierarchy name of the catalog For example, let us search for SKUs present in a hierarchy named ‘Secondary’. In this case, select the Operator as Equals and type the value as secondary. A list of all SKUs present in the secondary hierarchy will be displayed. |
Catalog Hierarchy Type | The following operators are available for this category:
| None | This filters data based on whether the hierarchy is primary or non-primary. If Is Primary is selected as the operator, all SKUs present in the primary hierarchy will only be displayed. |
Node Type | The following operator is available for this category:
| Root, Branch and Leaf are the 3 types of nodes available in a catalog. By default, all are selected which means that any condition applied will check for matches in all 3 types of nodes. | You can select any type or 2 types of nodes based on the search to be done. For example, if we need to search root nodes specifically, the other 2 options can be deselected and any condition applied will display matches w.r.t to root nodes only. |
Taxonomy | The following operator is available for this category:
| Based on the catalog selected, all the Hierarchy present in that catalog will be displayed as shown below.
In this case, there are 2 hierarchies. Depending on the SKUs to be filtered, select the respective hierarchy and the taxonomy structure present in the selected hierarchy is displayed as shown below.
In this case, the primary hierarchy is selected and the entire taxonomy structure is displayed. Note: You can select 1 or multiple hierarchies, as needed. | Here, the entire taxonomy structure present in the selected hierarchy is displayed. You can filter the data by selecting the nodes and all SKUs present in the selected nodes will be displayed. |
Taxonomy Level | The following operators are available for this category:
| You need to enter numeric values here. | This filters data based on the SKUs present in the node level specified. For example, we have a taxonomy hierarchy as Accessories > Watches > Digital and Accessories > Watches > Analog. If we want to filter SKUs present in nodes Digital and Analog, you can select the operator as Is Greater Than and specify the value as 2. Here, nodes Digital and Analog are at level 3. Hence, all SKUs present in these nodes will only be displayed. |
Taxonomy Name | The following operators are available for this category:
| Based on the operator selected, you need to enter the value. | This option filters SKUs based on the taxonomy name entered and the operator selected. If you select the operator as Does Not Contain and value as Sunglasses, all SKUs present in nodes which do not have the word Sunglasses in the node name will be displayed. |
Once the taxonomy query is selected, you can add additional taxonomy conditions.
Click the Add Taxonomy Condition Element 
icon and the following appears.
The options available for building additional conditions are the same as mentioned in Table 19: Taxonomy Conditions.
For example, we need to search for SKUs which belong to the primary hierarchy and are present in the branch nodes of the selected catalog. In this case, select the category as Catalog Hierarchy Type, and operator Is Primary. For the second condition, select the category as Node Type with operator as Equals Any of and deselect Root and Leaf as we only need SKUs present in Branch nodes as shown below.
Thus, when you search, only SKUs present in the branch nodes of the catalog existing in the primary hierarchy will be displayed. It is important that both the conditions are met as the conjunction AND is used here.
You can add multiple taxonomy conditions by clicking the 
icon and a combination of all will be considered when the search is executed. Also, you can click the Remove Taxonomy Condition Element 
icon next to the condition to remove it any time, if not relevant.
NOTE | You can also add a different category (attribute / assets / SKU) along with taxonomy and build conditions using 2 different categories or multiple categories, as required. |
Existence
You can build conditions using this condition category to locate specifically if attributes / validation failures / linked digital assets exist or do not exist for SKUs of the selected catalog. There are multiple categories available for the existence category based on which conditions can be built. Select the category as Existence and the following is displayed.
The following table provides an overview of the various categories, the operators applicable and the values to be entered while building a condition using the existence category.
Table 20: Existence Conditions
Query Category | Operators | Values | Comments |
|---|---|---|---|
Attribute | The following operators are available for this category:
| There are 2 options available:
| Here, you need to select the attribute name from the attribute master or select from the attribute group. For example, if you select an attribute Color and the operator as Does Not Exist, this condition will display a list of SKUs which do not have the attribute Color. |
Digital Asset Linkage | The following operators are available for this category:
| None | Based on the operator selected, this condition will filter all SKUs that have / do not have assets linked to it. |
Validation Failures | The following operator is available for this category:
| None. | Based on the operator selected, this condition will filter all SKUs that have / do not have validation failures. |
Once the existence category is selected, you can add additional conditions.
Click the Add Existence Condition Element 
icon and the following appears.
The options available for building additional conditions are the same as mentioned in Table 20: Existence Conditions.
For example, we need to search for SKUs having validation failures and do not have any digital assets associated with it. In this case, select the category as Validation Failure, and operator Exists. For the second condition, select the category as Digital Asset Linkage with operator as Does Not Exist as shown below.
Thus, when you search, only SKUs with validation failures and without any assets linked to it will be displayed. It is important that both the conditions are met as the conjunction AND is used here.
You can add multiple existence conditions by clicking the 
icon and a combination of all will be considered when the search is executed. Also, you can click the Remove Existence Condition Element 
icon next to the condition to remove it any time, if not relevant.
NOTE | You can also add a different category (attribute / assets / SKU / taxonomy) along with this category and build conditions using 2 different categories or multiple categories, as required. |
All the conditions created using any of the categories can be saved by clicking the Save Condition 
icon next to each category available. Once the condition is saved, it is saved and visible in the Saved Conditions tab. These conditions can also be used along with other categories to create complex conditions as explained here.
NOTE | An AND operator is present by default between 2 conditions of the same category. If a condition is being built using 2 attribute categories, both will be considered while displaying the result. However, while building conditions using 2 different categories such as attribute and SKU, you have the option to choose between AND / OR operators. If AND is selected, the result displayed will be based on the match found using all the conditions. If OR is selected, the result displayed will be based on the match found in any one condition between the categories. |
Any condition created can also be deleted. The condition created using multiple categories / same categories / saved conditions can be deleted completely by clicking the Remove Condition
icon next to the Query Category.
Let us understand how to build a condition using condition categories as well as saved conditions.