Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0044887Retail ModulesWeb POSpublic2020-08-25 14:382020-08-27 07:30
Reporterrafaroda 
Assigned ToRetail 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0044887: External Order Loader synchronizedProcessing=false: Data Import Entries type should be External Order
DescriptionExternal Order Loader synchronizedProcessing=false: Data Import Entries type should be External Order http://wiki.openbravo.com/wiki/Retail:Order_Loading_WebService#Synchronized_processing [^]

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

In Data Import Entries the register should go with type External Orderand message going to a Success or Error status

So there is no way to do a proper troubleshoot of the situation of external orders loaded
Proposed SolutionIn Data Import Entries the register:
* The record should be External Order: KO today
* The JSON received by the Data Import Entry should be registered in any case in JSON Info
Additional Information
TagsNOR
Relationships
related to defect 0044885 closed rafaroda External Order Loader synchronizedProcessing=true: Data Import Entries in Initial Status and no error info 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2020-08-25 14:38rafarodaNew Issue
2020-08-25 14:38rafarodaAssigned To => Retail
2020-08-25 14:38rafarodaResolution time => 1599429600
2020-08-25 14:38rafarodaTriggers an Emergency Pack => No
2020-08-25 14:39rafarodaTag Attached: NOR
2020-08-25 14:39rafarodaRelationship addedrelated to 0044885
2020-08-27 07:30marvintmNote Added: 0122366
2020-08-27 07:30marvintmResolution time1599429600 =>

Notes
(0122366)
marvintm   
2020-08-27 07:30   
After further internal discussion, we will not be fixing this issue for now. The reason is that although it is a bit inconvenient that import entries are created associated with the Order datatype, specially for logging, if we change this we would also need to implement the associated Import Entry Processor, and orders would be processed in a separate queue in Import Entry. This change has several implications that currently we are not very comfortable with.