1. dyfrig
  2. RO CSVI
  3. Friday, 16 February 2018
  4.  Subscribe via email
I am trying to use CSVI to update the visibility of J2Store products. I have exported the sku and visibility fields, corrected the visibility field and am now trying to import the new values. Instead of updating the visibility field of the existing product it creates a new product. I believe I have come across this problem before and, contrary to the tutorial on your site, it required an additional field to the sku to recognise it as an existing product but I can't recall which field.

I have attached a sample csv file sku_visibility.csv
(I've tried with and without quotes)

Also a backup of the template I'm using [attachment]csvi_templates_http://www.bysabawd.cymru_20180216.xml[/attachment]

Also the log of a run com_csvi.log.233.zip .


I am adding this at a later stage as I have found that an earlier attempt today to run this on a larger import had actually removed many of the articles as J2store products, This run timed out so I was then trying again with a small sample and this was failing. I have attached the log from the earlier run. I will now be attempting to restore the data to the situation it was in before this morning's run. Hopefully by importing all the fields exported I can, at least, get it back to how it was. I will do this on a small batch. By the way this is a live site.
[attachment]098b9d70c2d0806868ffa6e0efe493da[/attachment]
Accepted Answer Pending Moderation
Hello,
I am trying to use CSVI to update the visibility of J2Store products. I have exported the sku and visibility fields, corrected the visibility field and am now trying to import the new values. Instead of updating the visibility field of the existing product it creates a new product. I believe I have come across this problem before and, contrary to the tutorial on your site, it required an additional field to the sku to recognise it as an existing product but I can't recall which field.

Do these Sku's are already there in J2Store variant table? The debug log shows message that "No product id found for sku 9780954757847" and same for other skus and this is the reason why new products are created. To identify a product and its id CSVI uses only sku field.

I am adding this at a later stage as I have found that an earlier attempt today to run this on a larger import had actually removed many of the articles as J2store products, This run timed out so I was then trying again with a small sample and this was failing. I have attached the log from the earlier run. I will now be attempting to restore the data to the situation it was in before this morning's run. Hopefully by importing all the fields exported I can, at least, get it back to how it was. I will do this on a small batch. By the way this is a live site.

We always suggest to run only few records of import and if everything goes without an issue run a mass import particularly when it is a live site.
Kind regards,

Tharuna

=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
  1. more than a month ago
  2. RO CSVI
  3. # 1
Accepted Answer Pending Moderation
I've now been experimenting with an offline copy of the website, I'm still finding that despite checking that the sku exists and is in the variant table it still creates a new product. I have attached a word document with several screenshots of the site and database. I have also attached the import file (1 record only) and the logfile.
Attachments (3)
  1. more than a month ago
  2. RO CSVI
  3. # 2
Accepted Answer Pending Moderation
Hello,
Thank you for sending the details. I was able to find the cause for the issue. CSVI uses SKU as title and alias is generated from this title and default catid as 2 for uncategorised if alias and catid are not set in import file. The existing article is retrieved from these alias and catid values and since they don't match to your existing content a new article has been created. Please add alias and catid fields to your import file and check the import. I will add few lines to our J2Store document on this. In addition to these you also need to load the attached patch file before running your import. Let me know if it solves it.

patch_j2store_2018_02_21.zip
Attachments (1)
Kind regards,

Tharuna

=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
  1. more than a month ago
  2. RO CSVI
  3. # 3
Accepted Answer Pending Moderation
Just a quick update to say that this seems to be working for a test file on my local server. Before I run it on my online server I need to fully undo the damage caused when I first tried to do this and be quite careful in the preparation of the new import file so it'll probably take me a few more days as I'm quite busy with other matters. I'll update the call when I'm happy that the issue is fully resolved.
  1. more than a month ago
  2. RO CSVI
  3. # 4
Accepted Answer Pending Moderation
Hello,
Thank you for an update. We will wait for your feedback.
Kind regards,

Tharuna

=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
  1. more than a month ago
  2. RO CSVI
  3. # 5
Accepted Answer Pending Moderation
It's all working now. Thanks for your help.
  1. more than a month ago
  2. RO CSVI
  3. # 6
  • Page :
  • 1


There are no replies made for this post yet.
Be one of the first to reply to this post!