Pos3/5/FNB: Why I unable to see updated transaction even though sync is successful?: Revision history

Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom.
Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit.

5 April 2022

  • curprev 07:5807:58, 5 April 2022PeterT talk contribs 976 bytes +976 Created page with "<u><b>Question :</b></u> Why I unable to see updated transaction even though sync is successful? <u><b>Possible Reason :</b></u> You are using Rev169 and higher version for AutoCount POS. <u><b>Solution :</b></u> At newer version than rev169, we have optimized sync logic which the sync will continue to sync even though having error. The error will be brought back to backend for further troubleshooting. Now it could be caused by some transaction having error issue...."