Feature Pack 5 or later

Troubleshooting: Incorrect product sequences

Product sequences that are set in categories are not displayed correctly in starter stores with WebSphere Commerce search.

Problem

The sequence assigned to products is incorrect in starter stores with WebSphere Commerce search.

Solution

By default, the WebSphere Commerce search index must be re-indexed before the changes take affect in the storefront.

To resolve this issue, ensure that you trigger a search re-index.

Feature Pack 5 or later

Events that trigger search re-indexes

The search index is triggered for re-indexing when certain actions take place within WebSphere Commerce. Re-indexing is required to avoid working with stale data, ensuring that the content you are working with or previewing is currently up-to-date.

In the Management Center, with workspaces enabled:
  • Task group commit
  • Store preview
  • Show facets (catalog entry index)
  • UpdateSearchIndex scheduler job
    Note: This scheduler task triggers re-indexing only on the base index. It skips workspace indexes to prevent unnecessary re-indexing caused by uncommitted changes.
In the Management Center, with workspaces disabled:
  • Store preview
  • Show facets (catalog entry index)
  • UpdateSearchIndex scheduler job
In the Aurora starter store:
  • UpdateSearchIndex scheduler job.
    Note: This scheduler job detects changes made from the authoring server using the TI_DELTA_CATENTRY and TI_DELTA_CATGROUP temporary database tables. That is, after the quick publish task is approved, the runtime automatically publishes the search change history to the temporary tables in both the staging and production databases. It then launches a re-indexing for emergency fixes from the production server.
Using utilities:
  • The di-preprocess utility when run with the -workspace workspaceId parameter.
  • The di-buildindex utility when run with the -workspace workspaceId parameter.

For more information, see Index synchronization and delta updates in WebSphere Commerce search.