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
We've been working a store that has their data all over the place and have build a bunch of custom processors on top of the existing ones to make everything work. One issue we've seen is that if there is a significant number of failures on any particular type of import, usually that means that someone needs to go follow up in some capacity.
If it were possible to reconstruct the failed rows of the CSV and allowed that to be downloaded, that could really be useful in those failure cases.
I've personally done that with some console-fu, but it would be pretty easy to add a "Download failed rows" button to the import page. Would this enhancement be useful to others?
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It might be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It might be closed if no further activity occurs. Thank you for your contributions.
We've been working a store that has their data all over the place and have build a bunch of custom processors on top of the existing ones to make everything work. One issue we've seen is that if there is a significant number of failures on any particular type of import, usually that means that someone needs to go follow up in some capacity.
If it were possible to reconstruct the failed rows of the CSV and allowed that to be downloaded, that could really be useful in those failure cases.
I've personally done that with some console-fu, but it would be pretty easy to add a "Download failed rows" button to the import page. Would this enhancement be useful to others?
The text was updated successfully, but these errors were encountered: