Skip to main content
All CollectionsModulesInvoices
Sync Error "Another Objectstore with '' already exists [Support ID: adOmOWEB031%7EZ1BwYP5h0ML4Lqb-MszDfQAAABE] Could not create objectstore record. Use a unique value instead."
Sync Error "Another Objectstore with '' already exists [Support ID: adOmOWEB031%7EZ1BwYP5h0ML4Lqb-MszDfQAAABE] Could not create objectstore record. Use a unique value instead."

This guide explains how to resolve the sync error caused by duplicate attachment names when syncing invoices in ProcureDesk.

Updated over a month ago

Error Message

The following error is displayed during syncing:
​"Another Objectstore with '' already exists [Support ID: adOmOWEB031%7EZ1BwYP5h0ML4Lqb-MszDfQAAABE] Could not create objectstore record. Use a unique value instead."

Root Cause

The error occurs because the supporting document and the invoice attachment associated with the invoice have identical file names. This conflict prevents the system from syncing the invoice correctly.

Workaround

Renaming the attachment file resolves the issue.


Steps to Resolve

  1. Identify the Invoice with Sync Issue

    • Navigate to the invoice showing the sync error.

  2. Check Attachments

    • Review the attachments linked to the invoice (supporting documents and invoice attachment).

    • Confirm if the file names are identical.

  3. Rename the Attachment

    • Download the attachment causing the issue.

    • Rename the file to a unique name (e.g., add a timestamp or suffix to differentiate it).

    • Re-upload the renamed attachment to the invoice in ProcureDesk.

  4. Retry Sync

    • Attempt to sync the invoice again by clicking on Actions > Send for Integration.


FAQs

  1. How do I identify which attachment is causing the issue?

    • Review the attachments under the invoice details. If the file names are identical, they are likely the cause of the issue.

  2. What should I do if the issue persists after renaming?

    • Contact the ProcureDesk Support team for further assistance with detailed screenshots and the error message.

Did this answer your question?