New UX import error log

leahorata024_*15065
leahorata024_*15065
in User Experience

Hi,

 

Would like to ask if anyone have experienced not getting all errors made from the import in New UX error log?

 

Below is the current scenario during the upload:

 

1.  Loaded the csv file  with different period format (Y-M) from the import definition (M-Y) and with one item that is not existing on the list.

 

Currently, it's correct that the error message for period will be shown in the log but nothing else comes after this. The error for the not existing item were not included.

 

Only when we have fixed the time period mapping during the second import that the user was notified.

 

Is there a way that we could see both errors during the first import?

 

Thanks!

Tagged:

Answers

  • susanduncan
    susanduncan
    edited December 4

    Hello, I think you should ensure that your import action is configured to log all types of errors. Sometimes, settings may be adjusted to only capture specific errors. Before the import, consider adding a validation step in your process to check for valid items and period formats. This can help catch errors before the import runs. f possible, modify your import process to handle both checks (period format and item existence) and log all errors at once. This might involve using a staging model to validate the data before importing it into the main model.

Categories