Closed arobirosa closed 1 year ago
update ClassAttributeAssignment[batchmode = true]; classificationAttribute(code, systemVersion(catalog(id[default = ClassificationCatalog]), version[default = 1.0]))[forceWrite = true, unique = true]; attributeValues(code); systemVersion(catalog(id), version)[forceWrite = true, unique = true][default = ClassificationCatalog:1.0]; ; categories ; test ; species ;iguana
Where the attributes cateogries and species don't exist.
Michael Wölm just gave me a good tip to show more information about the log:
Inside the method org.areco.ecommerce.deploymentscripts.impex.impl.LocalizedImpexImportService#importImpexFile(java.io.InputStream) Get the cronjob from the impex result and store it in the execution result.
This allows the developers to see the logs of the impex cronjob.
Now the impex cronjob and the lastest log file are shown in the execution in the backoffice.
Describe the bug When there is an error in an impex, the stacktrace stored in the areco execution is useless and no error is shown in the console on hybris servers in SAP cloud. And kibana don't show any error.
To Reproduce Steps to reproduce the behavior:
Expected behavior The execution result with the error contains a stacktrace or a log file providing information about the error in the impex.
As workaround I ran the impex in HAC and look for errors.
Log entries None
Screenshots None
Additional context none