modmore
return insert ids of new resources
I've been importing lists of sub-categories for products to live in (over 3000 products), and created all the sub-categories for each category in a single import, then adding the products for each sub-category in another import. This requires finding the subcategories and checking the new resource id's before the next batch.
It would be nice if I could get the ids of the newly created resources back as a 'report' of sorts when the import finishes so that I could tie them up easily with the next stage of importing.
Unless someone knows a better way to do this !?
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
With such a complex multi level import you might be best off using a custom import script..
It would be possible to create some sort of report (sounds great for 2.0), but I'm not sure what good a list of hundreds IDs would do - you can already find them in the resource tree after all. Op 4 dec. 2012 01:24 schreef "Christian Hanvey" [email protected] het volgende:
I've been importing lists of sub-categories for products to live in (over 3000 products), and created all the sub-categories for each category in a single import, then adding the products for each sub-category in another import. This requires finding the subcategories and checking the new resource id's before the next batch.
It would be nice if I could get the ids of the newly created resources back as a 'report' of sorts when the import finishes so that I could tie them up easily with the next stage of importing.
Unless someone knows a better way to do this !?
— Reply to this email directly or view it on GitHubhttps://github.com/Mark-H/importX/issues/41.
It's not actually that difficult to perform a multi-stage import - a custom script would take longer to make (and debug!).
In my case the subcategories are scattered across different categories - that's why I was thinking it would be helpful to have a list of returned ids rather than search through the document tree.
To update the next stage of my import with the new parent ids, it would be easy to tie a list of ids back up to my original csv file. I thought it would be relatively simple but it's really not a biggie - just a suggestion.
It probably would be qiite straightforward to dump the resource ids as it creates it, just thinking out loud.. in an ideal world importx would just "get" the multilevel import. Op 4 dec. 2012 01:51 schreef "Christian Hanvey" [email protected] het volgende:
It's not actually that difficult to perform a multi-stage import - a custom script would take longer to make (and debug!).
In my case the subcategories are scattered across different categories - that's why I was thinking it would be helpful to have a list of returned ids rather than search through the document tree. To update the next stage of my import with the new parent ids, it would be easy to tie a list of ids back up to my original csv file. I thought it would be relatively simple but it's really not a biggie - just a suggestion.
— Reply to this email directly or view it on GitHubhttps://github.com/Mark-H/importX/issues/41#issuecomment-10979544.