Data not updating in Commerce Data Exporter feeds and changelog errors

This article provides a solution for fixing data synchronization issues caused by using the wrong view id in the Data Exporter Mview subscription. The Mview subscription is used to track changes for database tables.

Description description

Environment

Issue/Symptoms

The error occurs if the installed SaaS Data Export version is 103.3.0 or later, and the code directly references the catalog_data_exporter_products index.

Merchants may find that data updates are missing from the Catalog Data Exporter feed tables and see the following errors in the cron job logs:

[ 2024-05-27T19:00:04.627604+00:00]  report.
        ERROR: Cron Job
        indexer_clean_all_changelogs has an error: Table
        catalog_data_exporter_products_cl does not exist. Statistics:
        {"sum":0,"count":1,"realmem":0,"emalloc":0,"realmem_start":305135616,"emalloc_start":283210384} [ ]  [ ]

Cause

Due to name changes in feed tables, indexes, and change log tables in the Commerce Data Export version 103.3.0 release, the Mview subscriptions in custom extensions that use Commerce Data Export extensions may not work properly.

In this case, the table does not exist error occurs because the catalog_data_exporter table name was changed to cde_products_feed, and you have custom code that references the old name in the Data Exporter Mview subscription.

Resolution resolution

In the customized extension, edit the Mview configuration file (./etc/mview.xml) to change the catalog_data_exporter_products table name to cde_products_feed.

The following example shows the code that specifies the tables tracked by the Mview subscription:

<view id="cde_products_feed" class="Magento\CatalogDataExporter\Model\Indexer\ProductFeedIndexer" group="indexer">
        <subscriptions>
        <table name="custom_table" entity_column="product_id" />
        </subscriptions>
        </view>

Related Reading