microsoft / microsoft/Dynamics365Commerce.Solutions

Offline data sync failed - The offline transaction data could not be purged from the offline database

Open
#383 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
80
Forks
38
PR merge metrics
No merged PRs in 30d

Description

We added a custom field to the RetailTransactionTable and created an extension table called RetailTransactionTable_DLX, as indicated in the CDX extensibility documentation.
When creating an offline transaction and then switching back online, we encounter an error during the purge of records from the offline table.
The error message is: "Offline data sync failed. Offline may not be available or have the latest data. Please contact your administrator for further assistance." Error codes: "ASYNC_CLIENT_FAIL_PURGE_OFFLINE_TRANSACTION_DATA" Error message: "The offline transaction data could not be purged from the offline database."

Store commerce version is the 9.54.25182.8.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the CDX extensibility documentation and the RetailTransactionTable/RetailTransactionTable_DLX extension setup first. Reproduce the offline transaction flow on Store Commerce 9.54.25182.8 and investigate the ASYNC_CLIENT_FAIL_PURGE_OFFLINE_TRANSACTION_DATA failure; done means offline transaction data is purged successfully after returning online.

Written by the indexing model from the issue text.

Assessment

Domain
database
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.