Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0030835
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Web POSmajoralways2015-09-16 12:542015-10-07 16:54
ReportermalsasuaView Statuspublic 
Assigned Tomarvintm 
PriorityhighResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSLinux 32 bitDatabasePostgreSQLJava version1.6.0_18
OS VersionCommunity ApplianceDatabase version8.3.9Ant version1.7.1
Product VersionRR15Q2.3SCM revision 
Review Assigned Tomarvintm
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0030835: error to sync a receipt from terminal, but it is not deleted from terminal and it is not saved in errors while importing

Descriptionwhen the JSON of receipt is incorrect (createdby and updatedby are null), when the receipt is synced, it is not saved in error while importing data, and never is removed from local database
Steps To Reproduce. in offline: create a receipt
. update the json, updating the createdby and updatedby to null
. go online
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
has duplicate defect 0029871RR15Q3 closedaaroncalero Web POS orders not synchronizing 

-  Notes
(0080438)
Orekaria (administrator)
2015-09-16 19:11

There is no way to create a bad order
What are the customer actions that lead to this ticket?
What are the expected actions?
(0080448)
malsasua (developer)
2015-09-17 10:01

when the sync process fail by this reason (createdby in json is null), the receipt should be stored in Errors while importing.
I think that, in the sync process, one exception will be raised and it is not managed. For this reason the process does not finish and the receipt is not stored in errors while importing
(0080860)
marvintm (manager)
2015-10-07 15:33

Due to latest changes to the DataSynchronizationProcess class this problem doesn't happen anymore.

- Issue History
Date Modified Username Field Change
2015-09-16 12:54 malsasua New Issue
2015-09-16 12:54 malsasua Assigned To => Retail
2015-09-16 12:54 malsasua Resolution time => 1444255200
2015-09-16 12:54 malsasua Triggers an Emergency Pack => No
2015-09-16 19:11 Orekaria Note Added: 0080438
2015-09-16 19:11 Orekaria Status new => feedback
2015-09-16 21:18 Orekaria Assigned To Retail => malsasua
2015-09-17 10:01 malsasua Note Added: 0080448
2015-09-17 10:01 malsasua Status feedback => new
2015-10-05 12:10 Orekaria Assigned To malsasua => marvintm
2015-10-05 12:10 Orekaria Status new => scheduled
2015-10-07 15:33 marvintm Review Assigned To => marvintm
2015-10-07 15:33 marvintm Note Added: 0080860
2015-10-07 15:33 marvintm Status scheduled => closed
2015-10-07 15:33 marvintm Resolution open => no change required
2015-10-07 16:54 malsasua Relationship added has duplicate 0029871


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker