Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0044885Retail ModulesWeb POSpublic2020-08-25 14:352020-09-22 13:52
Reporterrafaroda 
Assigned Torafaroda 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0044885: External Order Loader synchronizedProcessing=true: Data Import Entries in Initial Status and no error info
DescriptionExternal Order Loader synchronizedProcessing=true: Data Import Entries in Initial Status http://wiki.openbravo.com/wiki/Retail:Order_Loading_WebService#Synchronized_processing [^]

Steps To ReproduceInsert via the External Order Loader a JSON with synchronizedProcessing=true

In Data Import Entries the register must register the JSON, the reponse message, and going to a Success or Error status, not keep in Initial

So there is no way to do a proper troubleshoot of the situation of external orders loaded.

Moreover, this record in Initial never goes to Data Import Entry Archive so it pollutes the Data Import Entry table/window.
Proposed SolutionIn Data Import Entries the register:
* The record should be External Order: OK
* The JSON received by the Data Import Entry should be registered in any case in JSOn Info
* If error, the Status = Error and the error message should be logged in Error Info
* If Success, the Status = Success and the response message should be logged in Response Info
Additional Information
TagsNOR
Relationships
related to defect 0044887 new Retail External Order Loader synchronizedProcessing=false: Data Import Entries type should be External Order 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2020-08-25 14:35rafarodaNew Issue
2020-08-25 14:35rafarodaAssigned To => Retail
2020-08-25 14:35rafarodaResolution time => 1599429600
2020-08-25 14:35rafarodaTriggers an Emergency Pack => No
2020-08-25 14:35rafarodaTag Attached: NOR
2020-08-25 14:39rafarodaSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=21535#r21535
2020-08-25 14:39rafarodaRelationship addedrelated to 0044887
2020-08-26 06:50rafarodaSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=21536#r21536
2020-08-29 13:01AugustoMauchNote Added: 0122443
2020-08-29 13:03AugustoMauchNote Added: 0122444
2020-09-04 04:55ranjith_qualiantech_comAssigned ToRetail => ranjith_qualiantech_com
2020-09-10 10:43ranjith_qualiantech_comStatusnew => scheduled
2020-09-14 06:33marvintmNote Added: 0122980
2020-09-14 06:33marvintmAssigned Toranjith_qualiantech_com => rafaroda
2020-09-14 06:33marvintmStatusscheduled => feedback
2020-09-22 13:52marvintmReview Assigned To => marvintm
2020-09-22 13:52marvintmNote Added: 0123287
2020-09-22 13:52marvintmStatusfeedback => closed
2020-09-22 13:52marvintmResolutionopen => no change required

Notes
(0122443)
AugustoMauch   
2020-08-29 13:01   
This issue also has performance implications. Because there is always import entries in Initial status, the import entry manager never sleeps. In less than 2 hours it has executed the query to get the pending import entries 153000 times.
(0122444)
AugustoMauch   
2020-08-29 13:03   
If the proposed solution is not feasible (because with synchronizedProcess=true orders are not imported using the import entry manager), maybe another approach would be to create the import entries with Success status
(0122980)
marvintm   
2020-09-14 06:33   
We have been unable to reproduce this issue so far either in pi or in 20Q3. We are in contact with Rafa Roda to try to find a way to reproduce it, as it does seem it happened in the customer environment
(0123287)
marvintm   
2020-09-22 13:52   
After further analysis, we have realised that the problem was that provided message ids were not in upper case, which is a requirement to follow Openbravo convention of UUIDs. After this has been changed, the EOL correctly sets import entries to 'Processed' status.