You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case of very large files, waiting time for parsing to finish is considerably long.
Instead, just complete the CSV headers to key mapping and return the mapping. This will fasten the process and reduce the waiting time
Also, Import Successful message is displayed too early and this wording will confuse user in thinking that the actual CSV file has been mapped, parsed and uploaded/imported. So we need some mechanism where we display Import Successful message only after the data is really "imported" and not just parsed.
Proposed changes
Addition of onCSVHeadersMapped?: (data: any) => Promise<void>; to CSVImporterProps
Why this change is needed?
Import Successful
message is displayed too early and this wording will confuse user in thinking that the actual CSV file has been mapped, parsed and uploaded/imported. So we need some mechanism where we displayImport Successful
message only after the data is really "imported" and not just parsed.Proposed changes
onCSVHeadersMapped?: (data: any) => Promise<void>;
toCSVImporterProps
case StepEnum.MapColumns:
success callbackThe text was updated successfully, but these errors were encountered: