How is cobby notified about changes from Magento?

This article explains how changed values from Magento can be taken over and applied in cobby and what can cause problems here.

As soon as a change is made in Magento, the Magento model informs all dependent business logics. In the case of cobby, this is either the cobby Indexer or the corresponding Magento events (Event/Observer). This adds the changed elements (products, categories, attributes) to the cobby queue within the Magento installation. Each change gets its own number (queue ID). Subsequently, the cobby service is notified. This then loads all entries from the cobby queue and processes the changes together in a transaction (transaction ID). Products affected by changes receive a red status in Excel, provided Excel is open.

From this point on, the change will also appear in the change history in the cobby customer center as a separate entry with the cobby queue ID as the transaction ID.

Note: A developer with database access can thus also determine within the Magento installation which user triggered the change.

Q: How can I tell if the change in history is from cobby or Magento?

The transaction ID provides information about where a change came from. Characteristics for Magento are a consecutive number, while the transaction ID (from cobby) is individual.

In rare cases it can happen that an extension or a manual entry in the database bypasses the Magento model. This shows up in the Magento backend and in cobby by different values being displayed. In this case, it is useful to take a look at the change history to see when such a manual entry has been made.

Please note: Often this is noticed first when working with cobby, but in almost all cases this causes problems in all Magento functions, because the business logics are not aware of this.