Developer forum

Forum » Development » More headache with the import / export module

More headache with the import / export module


Reply
Hi guys (probably Morten :-) )

I've updated my live solution to 19.2.2.1 now, and everything seemed fine at first.
But now the client mails me that related products aren't updated.

I've run a few tests both live and locally, and i can't get related products to change.

Is it another bug in the import module?

Regards
 Martin

Replies

 
Reply
Hi Martin!
I probably don't understand you correctly;-(. Since I can not reproduce the situation. I've completed the import of products. Existed products were updated, and their lists of related products are also were updated.

Please provide URL of your site and step by step instructions how to reproduce the error, I will check it.

Best regards,
Vladimir
 
Reply
 Hi Vladimir, 

The site i'm runnig the import on is www.pkc.dk.

The steps to start the import is:

- Go to Import / Export module
- Select pipeline "NAV product import"
- Run it

The product 103113 has 5 related products in the XML, but when you look eCom before and after import, there's 11 related products.

The XML is delivered from NAV, and has Type set to "Full"

Regards
 Martin
 
Reply
Hi Vladimir,

To further debug on this, i've tried playing around with the XML, and i've been able to recreate the error just by changing XML and importing.

Steps to reproduce:

1 - Import product with 5 related items. I used this XML


 
   
 
   
   
   
   
   
 



2 - Import product with more related items.


 
   
 
   
   
   
   
   
   
   
 



3 - Import product with fewer related items again


 
   
 
   
   
   
   
   
 



When you look up the product in eCom after doing the above steps, the product will have the related items from step 2, and not step 3.

I hope the XML is encoded on this forum :-)

Regards
 Martin
 
Reply
Okay, it didn't.

I've attached the post as a text file.
 
Reply
there
 
Reply
Really, old related products are not deleted. This is a bug, I registered it in our  bug tracking system at number #6410

Best regards,
Vladimir

 

You must be logged in to post in the forum