I have the following setup of import definitions for imports in uWebshop
- Import products
-- Import product variants
If I run Import products again, with a new xlsx-file, CMSImport warns me that Import product variants will be run as well. That's expected behavior.
Unexpected behavior though is that 'Import product variants' doesn't run with the new xlsx, but with an old one. The imported files are stored in App_Data\cmsimport prefixed with a guid, and I suspect that the child definition runs with an older version of the same file.
If I walk through the import definition of the child (and as such upload the new file), and save the import definition without running it, and then I run the parent import definition with the new file (and as such upload the new file again) it does import the child definition correctly, but I suspect that it still imports an old version. But since I've uploaded a new old version (so to speak), it seems to work.
The fix for now is running the child definition manually after I run the parent.
It's using the old one indeed. The message is only to warn you that child definitions will also execute. What you can do is add the excel file to a folder and use the url option to point to the excel file. Then you are always sure that the latest file is being picked up instead of the file you uploaded directly to the import definition.
Which file does a child definition use on re-runs?
I'm not sure if this is a question or bug report.
I have the following setup of import definitions for imports in uWebshop
- Import products
-- Import product variants
If I run Import products again, with a new xlsx-file, CMSImport warns me that Import product variants will be run as well. That's expected behavior.
Unexpected behavior though is that 'Import product variants' doesn't run with the new xlsx, but with an old one. The imported files are stored in App_Data\cmsimport prefixed with a guid, and I suspect that the child definition runs with an older version of the same file.
If I walk through the import definition of the child (and as such upload the new file), and save the import definition without running it, and then I run the parent import definition with the new file (and as such upload the new file again) it does import the child definition correctly, but I suspect that it still imports an old version. But since I've uploaded a new old version (so to speak), it seems to work.
The fix for now is running the child definition manually after I run the parent.
Hi Gijs,
It's using the old one indeed. The message is only to warn you that child definitions will also execute. What you can do is add the excel file to a folder and use the url option to point to the excel file. Then you are always sure that the latest file is being picked up instead of the file you uploaded directly to the import definition.
Thanks,
Richard
Why didn't I think about that myself?
Thanks.
is working on a reply...