Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
I am having an issue with the latest version of CMSImport. I have two unrelated imports set up, one for articles another for products. Unfortunately I am having some issues with them clashing. They are both using the same sql data source and have issues if they share ids. For example:
If I have an article with ID 1 and I run the import, all is fine. If I then run the products import and one of my products has the same ID (1) it will refuse to import. Additionally, if I select the delete old items option, it will delete any items from the other import which don't appear with an ID in this import.
If it helps, I have noticed that the CMSImportRelations table stores all of the imported items with the data source key "Sql serverIDx" so it is clearly not able to work out which import each thing is for. I suspect I can get around this by using SQL to rename the ID field but it's a little annoying!
This is by design. A relation is created based on [Data provider alias][Primary key name][Primary key value] so make sure primary key field is unique in your sql.
Richard, that is not super intuitive and I don't believe CMS Import warns you about it. My ID's clashed and now my data is in a bit of a mess.
Actually cost me half a day figuring this out.
Sorry to hear Robert,
With bulkmanager free version you can delete old records when needed.
That's okay, I figured it out but it was pretty frustrating. It seems it'd be an easy fix to include some extra meta data in the import log to eliminate this problem.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted