Excel upload error handling

[Wei Wang]

When using Excel Upload, if there is an error (i.e., element does not exist in the row/column headers), UX gives a somewhat misleading error message. Namely the part related to “valid cells will be saved”. Even in the simple example below, UX does not save the rows prior to the last element (where the error occurs).

More important would be having a better notification that gives some insight to the user where the error occurred. In this example, if the message said: “please check row 8” or or “please check the New Element row”, it would be a big win in helping users identify and correct the error. In the case of multiple errors, perhaps we can just identify the first error where the DBS API call error occurs to keep it simple.

‌

[Nikunj Patel]

+1 - this is important for us and critical to make it clear for users.

[lance.wang]

+1 clients need the clear notification

[Nikunj Patel]

Can we have an update on this?

[Ada Trajer]

This enhancement will be included in the upcoming 2022.06 FP2 release.

[Scott Wiltshire]

Removing milestone: 2022_Q1 (automated comment)