Index for Table xyz Not Unique

Modified on Thu, 20 Aug at 8:54 PM

Overview

In the QQube Configuration Tool, the synchronization log list may display a red failed entry when QQube cannot refresh a materialized view because a required index would no longer be unique.

Resolve every failed entry

A later synchronization that reports Success does not mean this earlier error corrected itself. The failed entry must still be reviewed and resolved.

The detailed synchronization log may contain a message similar to one of the following:

Detailed synchronization log message

<<<<<<<<<<<<<<<<<<<<<< 10/15/2027 06:44:57 PM >>>>>>>>>>>>>>>>>>>>>>
SybaseSession_ExecuteNonQueryCommand
ExecuteNonQuery
Index 'mvf_FINANCIALTBA' for table 'mvf_FINANCIALTBA' would not be unique
refresh materialized view "mvf_FINANCIALTBA"
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Detailed synchronization log message

<<<<<<<<<<<<<<<<<<<<<< 10/15/2027 06:44:57 PM >>>>>>>>>>>>>>>>>>>>>>
SybaseSession_ExecuteNonQueryCommand
ExecuteNonQuery
Index 'mvd_Item' for table 'mvd_Item' would not be unique
refresh materialized view "mvd_Item"
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Detailed synchronization log message

<<<<<<<<<<<<<<<<<<<<<< 10/15/2027 06:44:57 PM >>>>>>>>>>>>>>>>>>>>>>
SybaseSession_ExecuteNonQueryCommand
ExecuteNonQuery
Index 'mvd_LINE_CHECK_SDK_LINE' for table 'mvdf_LINE_CHECK_SDK' would not be unique
refresh materialized view "mvdf_LINE_CHECK_SDK"
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Detailed synchronization log message

<<<<<<<<<<<<<<<<<<<<<< 10/15/2027 06:44:57 PM >>>>>>>>>>>>>>>>>>>>>>
SybaseSession_ExecuteNonQueryCommand
ExecuteNonQuery
Index 'mvd_LINE_VENDOR_CREDIT_SDK_LINE' for table 'mvdf_LINE_VENDOR_CREDIT_SDK' would not be unique
refresh materialized view "mvdf_LINE_VENDOR_CREDIT_SDK"
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

What the Error Means

QQube attempted to refresh a materialized view, but the source data produced more than one record for a value that must remain unique.

The required correction depends on the materialized view named in the synchronization log.

Identify the Error Type

Log Pattern	Cause	Required Action
mvf_FINANCIAL...	A longstanding Intuit SDK behavior affects Financial Summary or Financial Summary by Class data models when the QuickBooks preference Show lowest subaccount only is enabled.	Clear the preference and reload the affected Financial Summary data models.
mvd_Item, mvd_Account, or another list view	Items, accounts, customers, vendors, classes, or another QuickBooks list were merged. The Intuit SDK does not identify the merge in a way that allows QQube to update the existing database safely.	Perform a complete QQube clear and reload.
mvdf_LINE_...	A QuickBooks name type may have changed, such as Other Name to Vendor or Vendor to Other Name. The Intuit SDK can return two records with the same unique identifier.	Perform a complete clear and reload. Escalate if the same error returns.
mvdf_LINE_VENDOR_CREDIT_SDK	A Vendor Credit contains an invalid inventory or Cost of Goods Sold entry associated with negative or positive inventory.	Submit the synchronization log to CLEARIFY Support so Engineering can identify the affected transaction.

Resolution

1. Financial Summary Materialized View

In QuickBooks, clear the Accounting preference Show lowest subaccount only.

QuickBooks Accounting preference with Show lowest subaccount only cleared

Reload the affected Financial Summary or Financial Summary by Class data models using both Run All and Clear all data on synch start.

QQube Run All and Clear all data on synch start options

Financial Summary reload scope

Only the affected Financial Summary data models must be reloaded for this error type.

2. Merged QuickBooks List

Perform a complete QQube clear and reload using both Run All and Clear all data on synch start.

Review When to Clear the Database and Reload.

3. Changed QuickBooks Name Type

Perform a complete QQube clear and reload.

If the same error returns, follow Rebuild and Verify a QuickBooks Company File, and then complete another clear and reload.

If the error still returns, select the specific synchronization log and use Send to CLEARIFY Support.

4. Vendor Credit Inventory or Cost of Goods Sold Entry

Create a CLEARIFY Support ticket and include the synchronization log. Engineering will identify the affected Vendor Credit transaction and provide the required correction.

Use QQube Support Options.

When CLEARIFY requests a copy of the QuickBooks company file, the file is handled confidentially. CLEARIFY can sign an NDA for your organization.

Expected Result

The duplicate source condition is removed, the affected materialized view refreshes successfully, and the synchronization completes without another index-uniqueness error.