Developer forum

Forum » Integration » Data integration are duplicating the Ecom Groups

Data integration are duplicating the Ecom Groups

George Nelzo Pereira
Reply

Have someone seen in data integration are duplicating the Ecom Groups (Using the ecomm provider) ?

The products are importing correct (making update) but the groups, are duplicating all time.

I'm using 8.4.1.2


Replies

 
Morten Snedker
Reply

Hi George,

I am pretty confident that this is caused by groups not being recognized on their key. Try selecting from the database, a group name that has been duplicated, but shouldn't have been. Now, take a look at the GroupID for these two groups.

If one group has the prefix "IMPORTED", it is because there has not been a match on key upon import, and the destination provider has assigned a key value automatically. If GroupID does NOT contain the prefix, it is because it was found/matched in the source.

 

Let me have a comment on the above.

 

Regards /Snedker

 
George Nelzo Pereira
Reply

Hi Morten.


I changed the integration (delete and create again with correct setup, before I didn't put the mapping to groupID) Now with a GroupID is still duplicating the Groups.

In the same setup (to Products) I didn't had a problem without or with (ProductID) and was not duplicating the products.

I took a print scr

http://www.screencast.com/t/m566fTU4tI7

http://www.screencast.com/t/fwy6hvWn

 
Morten Snedker
Reply

I think the problem is that it was messed up in the first place. Try clearing your groups entirely:

TRUNCATE TABLE EcomGroupRelations
TRUNCATE TABLE EcomGroupProductRelation
TRUNCATE TABLE EcomShopGroupRelation
TRUNCATE TABLE EcomGroups

As you may read in the documentation, the groups are matched on GroupID, GroupNumber, GroupName - in that order. So, if you clear the relevant tables related to groups, and given the setup in you screendumps, I would expect for ie group "Essential" to appear only once with GroupID/GroupNumber set to "1000".

Alternative to clearing groups, you may check the option "Remove missing rows" found on the Ecom Provider settings. Since you now have GroupID in the mapping, all groups with prefix "ImportedGROUP" ought to be removed from the database, having this option set on the destination (Ecom) provider.

Give it a go, and let me know how it turns out.

 

Best regards /Snedker

 
George Nelzo Pereira
Reply

Hi Morten,

I got that.

The first execution is ok (but the groups still have ImpotedGroup in GroupID)

When I execute the second time, they remove the Groups and create again, than I lost the reference Product x Groups

I made one video.

 

Here is the link: http://demo84.azureii.hupx.com.br/Files/Files/2014-05-13_1132_ProblemToImportGroups.swf

 
Morten Snedker
Reply
  1. First: If possible, use the GroupID in the "groups" column mappings for the products. I think that this may do the very difference between success and failure.

     
  2. If (1) does not help: Can I have you try splitting the job into two separate jobs - one for groups and one for products. Run group import first - check result in database. Then run product import, and once again check result in database.

 

Looking forward to your findings!

 

Regards /Snedker

 
Morten Snedker
Reply
This post has been marked as an answer

Hi George,

 

Just a follow-up on this one: as stated on the support case, the problem you experience is due to a difference in column data type between source and destination. You're source column for GroupID is most probably an integer, and source is nvarchar. Use your view for casting the value to type nvarchar, and you should be home-free! ;-)

 

I will emphasize this in the documentaion.

 

Regards /Snedker

Votes for this answer: 1

 

You must be logged in to post in the forum