How: In the “Add Multi-Search Fields” dialog, the Entity Type dropdown only offers the entity selected as base entity in Model step, “Item” in this example. We would like to use fields from other levels in the model as well as multi search fields and be able to select a field from the "Sku" level.
Why: We are using a flattened store. SKU number sits on the SKU level, not on the base entity. We can add it to Searchable Fields, but Multi-Search is locked to “Item”. Users who paste a list of SKU numbers can’t search on the identifier they actually have. Flattened stores are therefore less capable than classic stores for multi-search.
For Who:
Brand Store admins who configure Data settings for flattened stores.
End users of those stores, such as retailers and partners, who look up many products at once by SKU number.
Any customer using a flattened-store whose key identifier is below the base entity is likely affected too.
Impact:
Bulk lookup by SKU becomes possible in flattened stores.
Flattened and classic stores behave the same for multi-search, which removes a confusing limitation.
Additional context: this works for classic stores
Please, add your suggestion and feedback above to add to the insights used by Product team when deciding priorities and direction of the Inriver PIM.