Diagnosing a data discrepancy

Last update: October 31, 2024

CREATED FOR:

  • Developer

This article provides solutions for troubleshooting discrepancies between a Magento Business Intelligence (MBI) report and a query or third-party report.

Depending on the complexity of your analysis, generating the corresponding MBI report may require familiarity with a number of different facets of the platform. This checklist and the related links will help you understand the logic behind your report, allowing you to identify the source of any discrepancies.

  1. If another member of your team created the report, begin by confirming the objective and parameters of their analysis.

  2. Generate expected data points to compare to the MBI report based on a query, a third-party reporting tool, or a formula.

  3. Review and confirm the metric definition(s), either from the metric link in Report Builder or by visiting the System Summary tab:

    • Data table
    • Operation
    • Operand column, including its calculation if it is derived (via System Summary)
    • Timestamp
    • For subscription metrics: start and end dates
    • Filters, including those contained in any filter sets applied

  4. Review and confirm other data manipulation within the report:

  5. If the discrepancy involves recent data, confirm the latest available data point by consulting the Update Details section on the Connections page.

  6. If a metric used in the analysis is built on a table from your database where rows are ever deleted from that table, confirm with the MBI Support Team that the table is being checked for deleted rows, as well as the frequency of the recheck and the replication method for the table.

  7. Similarly, if columns used in the analysis can be modified after a row is added, confirm with support that these columns are being checked for modifications, as well as the frequency of the recheck.

Still stumped? Don’t worry - we’re here to help. Send us a request using these instructions.

Best practices for modifying database tables in the Commerce Implementation Playbook

Previous pageIndex is locked by another process
Next pageAdmin 2FA email notifications not being received

Commerce