Field name priority

As it is possible to ingest products and SKUs with arbitrary field names through the use of sku attributes and product metadata, it is possible to create a field with the same name as another field.

This should be avoided, since requests which only use the field name of a field, such as search request filters, will be ambiguous. To resolve the ambiguity, Ecommerce Search has an inbuilt priority on which SKU or product field requests will refer to.

Example

By accident, a field with the field name Url has been added to both StringAttribute and Metadata. On the search scope, Url has been added, expecting the URL value from Metadata to be returned. The returned URL, however, is incorrect, as StringAttribute has a higher priority than Metadata.

The priority list, in order of highest to lowest priority, is as follows:

  1. Product SearchableIds
  2. Product AlternativeSearchWords
  3. SKU SkuEan
  4. SKU SkuNo
  5. Product ProductNumber
  6. SKU SkuId
  7. Product ProductId
  8. SKU SkuName
  9. Product ProductName
  10. Product CategoryNames
  11. Product CategoryIds
  12. Product Categories
  13. Product ShortDescription
  14. Product LongDescription
  15. Product Price
  16. Product PriceGroup
  17. Product Inactive
  18. SKU Stock
  19. SKU StringAttribute
  20. SKU NumberAttribute
  21. SKU IntervalAttribute
  22. SKU Metadata
  23. Product Metadata
  24. Product Media