Closed priyancajogoo closed 1 year ago
Simplest solution would be to export results as CSV, leveraging existing feature on sfpegListCmp (see _PEGLIST repo). I shall give it a try rapidly. @priyancajogoo
Hello @pegros , will it be possible to export the result in the same format as the import file which will be an excel file? For large imports, there is also a delay between clicking the button and displaying the results. Will be possible to disable the import button or display a spinner after the import button is clicked to avoid multiple clicks?
Thank you.
@priyancajogoo I implemented a first version of the Summary export and tried to add a spinner for the initial upload. This is still work in progress but it should already help you.
FYI @jstukas
Hello @pegros, Will it be possible to make the component accessible in flow please? Thank you
@priyancajogoo I shall give it a try
@priyancajogoo I just added Flow Builder support (see commit c4da1c4) FYI @jstukas
Hello @pegros , could you give us an update on the status of the export functionality please?
Have you tried the latest version ? Is it not enough ?
Hello @pegros, Yes we have tried the latest version where the errors are exported in another tab. However it would be more helpful for users to receive the error on in the same sheet as the input with the error column in the last position (same as data loader/salesforce inspector's result format). Hence, users can simply correct the lines needed without having to do a find/vlookup.
Is your feature request related to a problem? Please describe. Regarding the import results are shown in an iteration using only the key. However for bulk imports the way the failures and success are shown is not convenient/ readable for end users.
Describe the solution you'd like The possibility to download the failures and success in a CSV/Excel file with the same columns as the import file + the Id of the success and errors of the failures.
Describe alternatives you've considered Having the excel import file headers and import results exposed as a property so it can be handled and exported by a parent component.
Additional context