Re: EasyPopulate 4.0 Support Thread
Okay, so it does appear that the products_model record for some reason is not getting updated, but other related information does... Need to chase that down because someone else that had requested the capability to import by products_id didn't mention this "issue" otherwise it wouldn't be one...
Here are the results of me importing the test products that were exported from my test category (single category only rather than the entire file) where the only change between export and import was the products_model for "model" 277 was to add three characters.:
Quote:
Filename: Full-EP2016Apr27-192924.csv
UPDATED! - Model: 275 | prod_attr | 1 | | Test Multi | Trying to | | | | | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | | 2016-03-18 | 10000 | | Test attri | --none-- | 1 | 0 | 0 | 0 | 0 | 0 | | | |
UPDATED! - Model: 276 | test_singl | 1 | | Test Attri | This produ | | | | | 15 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | | 2016-03-28 | 100 | | Test attri | --none-- | 1 | 0 | 0 | 0 | 0 | 0 | | | |
UPDATED! - Model: 277 | test_singl | 1 | Rdog1.jpg | Test Attri | This produ | | | | | 15 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | | 2016-04-01 | 100 | | Test attri | --none-- | 1 | 0 | 0 | 0 | 0 | 0 | | | |
UPDATED! - Model: 278 | test_doubl | 1 | | Test Attri | This produ | | | | | 16 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | | 2016-04-06 | 99 | | Test attri | --none-- | 1 | 0 | 0 | 0 | 0 | 0 | | | |
UPDATED! - Model: 279 | test_tripl | 1 | | Test Attri | This produ | | | | | 17 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | | 2016-04-06 | 100 | | Test attri | --none-- | 1 | 0 | 0 | 0 | 0 | 0 | | | |
UPDATED! - Model: 280 | add_attrib | 1 | | test add a | This is he | | | | | 25 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | | 2016-04-13 | 5 | | Test attri | --none-- | 1 | 0 | 0 | 0 | 0 | 0 | | | |
Finished Processing Import File
Updated records: 6
New Imported records: 0
Errors Detected: 0
Warnings Detected: 0
Memory Usage: 785064
Memory Peak: 1302016
Execution Time: 0 seconds.
What is being used to modify the file/store it as a CSV?
Re: EasyPopulate 4.0 Support Thread
To confirm, you have the primary key set as products_id and have it entered in the User defined products field?
here is my configuration
Title Value Action Uploads Directory EPtemp/
Uploads Directory Admin/Catalog true Info
Import/Export Primary Key products_id Info
Upload File Date Format m-d-y Info
Default Raw Time 09:00:00 Info
Upload/Download Prices Include Tax false Info
Verbose Feedback true Info
Show all EP4 Filetypes with Files true Info
Replace Blank Image false Info
Make Zero Qty Products Inactive false Info
Smart Tags Replacement of Newlines true Info
Advanced Smart Tags false Info
Debug Logging true Info
Maximum Quantity Discounts 3 Info
Split On Number of Records 2000 Info
Script Execution Time 60 Info
Convert Curly Quotes, etc. 0 Info
Convert Character 0x92 1 Info
Enable Products Meta Data 1 Info
Enable Products Music Data 0 Info
User Defined Products Fields products_id Info
Export URI with Prod and or Cat 0
Re: EasyPopulate 4.0 Support Thread
I downloaded a new file. I edited one product title by 5 characters.
removed, other than header line, all other unedited lines, saved the file with one record in it, uploaded and imported
the result was the same
Import Results
Filename: Full-EP2016Apr27-184246.csv
Finished Processing Import File
Updated records: 0
New Imported records: 0
Errors Detected: 0
Warnings Detected: 0
Memory Usage: 4867608
Memory Peak: 5363688
Execution Time: 0 seconds.
Re: EasyPopulate 4.0 Support Thread
Huh.. Go figure.. Can add a new product with a new model number, but it looks like the products_model field for "updating" didn't get incorporated in the update section... (looking strictly at the code) even though I have it (products_model) included as a user defined field.
So, in this case? (until I get it fixed as part of my very soon to be released 4.0.35 as I want to test the few changes I made), one would need to or could, duplicate the product information in the import file, while importing by products_id such that the first occurrence deletes the product (status 9), the second occurrence with the same products_id reloads it... But, *shucks* I guess there is a downside to that as if there are attributes and other data "dependent" on the products_id, then they may get removed/reshuffled as well... Okay, should have a fix momentarily for the UPDATE of the products_model when using products_id or blank_new as the import option.. You should still be getting a report of updated product though or some sort of error that either the primary key doesn't exist or there is a problem with the remaining data...
Thank you for pointing out this issue... It's a shame, I guess the update portion hadn't been fully flushed out because the insert works fine... Maybe the priorities on the project changed, I can't recall..
Re: EasyPopulate 4.0 Support Thread
Quote:
Originally Posted by
Carbonless
To confirm, you have the primary key set as products_id and have it entered in the User defined products field?
here is my configuration
Title Value Action Uploads Directory EPtemp/
Uploads Directory Admin/Catalog true Info
Import/Export Primary Key products_id Info
Upload File Date Format m-d-y Info
Default Raw Time 09:00:00 Info
Upload/Download Prices Include Tax false Info
Verbose Feedback true Info
Show all EP4 Filetypes with Files true Info
Replace Blank Image false Info
Make Zero Qty Products Inactive false Info
Smart Tags Replacement of Newlines true Info
Advanced Smart Tags false Info
Debug Logging true Info
Maximum Quantity Discounts 3 Info
Split On Number of Records 2000 Info
Script Execution Time 60 Info
Convert Curly Quotes, etc. 0 Info
Convert Character 0x92 1 Info
Enable Products Meta Data 1 Info
Enable Products Music Data 0 Info
User Defined Products Fields products_id Info
Export URI with Prod and or Cat 0
Would say similar:
Quote:
Uploads Directory secret_folder_with_no_end_slash
Uploads Directory Admin/Catalog true Info
Import/Export Primary Key products_id Info
Upload File Date Format m-d-y Info
Default Raw Time 09:00:00 Info
Upload/Download Prices Include Tax false Info
Verbose Feedback true Info
Show all EP4 Filetypes with Files true Info
Replace Blank Image false Info
Make Zero Qty Products Inactive false Info
Smart Tags Replacement of Newlines true Info
Advanced Smart Tags false Info
Debug Logging true Info
Maximum Quantity Discounts 3 Info
Split On Number of Records 2000 Info
Script Execution Time 60 Info
Convert Curly Quotes, etc. 0 Info
Convert Character 0x92 1 Info
Enable Products Meta Data 1 Info
Enable Products Music Data 0 Info
User Defined Products Fields products_id Info
Export URI with Prod and or Cat 0 Info
Believe there is still an open question. What is being used to edit the csv file/save it?
If you in fact open the file with a plain text editor does it look correct? (typically quotes around each set of text, that is then separated by a comma, with some form of carriage return at the end of each line.)
Re: EasyPopulate 4.0 Support Thread
Thank you. I will test first thing in the morning.... Using OpenOffice as per suggested!
Thank you for your well used time.
Re: EasyPopulate 4.0 Support Thread
FWIW, I also changed the stored folder name for files to include a / at the end of it, reperformed import with same/similar results as previously reported...
Re: EasyPopulate 4.0 Support Thread
Found and fixed the issue(s) with updating while not using products_model as the primary key. Haven't uploaded the fix quite yet, but will be up soon. Want to also check some of the changes made to the featured products area to address some previously pointed out issues.
Not yet sure about the 0 products updated issue... please check for any log errors in the logs directory...
Re: EasyPopulate 4.0 Support Thread
Great news. I eagerly await your upgrade. Thank you for the time and attention to my request and giving great support.
Re: EasyPopulate 4.0 Support Thread
Quote:
Originally Posted by
Carbonless
Great news. I eagerly await your upgrade. Thank you for the time and attention to my request and giving great support.
While I did notice a minor difference in the provided code and what was on my test site, I hope that it is the smoking gun for why import with product_id as the primary key was an issue. I also was trying to think back on why the problem existed here versus previous testing and development and it appears that in the spanse of local git work that the corrections may have existed on another branch or were incorporated specifically for the requestor and didn't make its way into a specific branch. :/ If nothing else, a reason to identify an issue when discovered rather than walking away. :) Thank you for identifying the issue and working with me to resolve. Of course proof to be seen.
I would have applied the changes to my 4.0.35 path, but I was going to apply it to the changes to improve the featured import. When I went to test the modifications to the featured import at least on ZC 1.5.5, I noticed that featured product control treats dates of 0001-01-01 as a date in 2036, so I need to look into that operation from the ZC side. But, once I get back to my computer I will apply the change of this discussion directly to the master for the branch and deal with the featured issues separately.