EasyPopulate 4.0 Support Thread

I'm using Easy Populate 4.0.30 - Beta 06-27-2015

I define the following fields in admin setting in Easy Populate:
User Defined Products Fields: products_ordered,products_length,products_width,products_height,products_ready_t o_ship

I exported Complete Products (with Metatags) then removed all but either id or model forgot which is required and the defined above and imported back with the defined fields populated as I needed them to be. That's all I did which I believe reset the quantity ordered as I described.

Quote:

---

Originally Posted by marcopolo

I'm using Easy Populate 4.0.30 - Beta 06-27-2015

I define the following fields in admin setting in Easy Populate:
User Defined Products Fields: products_ordered,products_length,products_width,products_height,products_ready_t o_ship

I exported Complete Products (with Metatags) then removed all but either id or model forgot which is required and the defined above and imported back with the defined fields populated as I needed them to be. That's all I did which I believe reset the quantity ordered as I described.

---

[So, here is what I understand in “date” order and therefore remain perplexed if there is an issue or not:
At point A a backup of the database was made.

At point B an export was made, the file modified to only include the primary reference key and user defined fields that were to be updated with whatever was in the import file.

At point C, the import file with the primary key and user defined data fields was imported causing the product identified by the primary key to be updated with whatever was present (or “absent”) in the user defined fields. The data for each field had been updated as desired/requested and all fields were present in the file. This included a field called products_ordered.

At point D (call it today), a comparison of the live database to the backup made at point A shows that everything is the same except for the data that was stored at point C. But the data in the products_ordered field is now zero instead of the quantity identified in the file at point C.

So question(s) are:
1) Did the import file at point C actually include the products_ordered field or not?
1.a) If it did, how do the values identified there relate to what is/was in the database?
2) If you were to again upload just a single row of data that included the products_ordered field and information for that field, what happens to the information of that product and field?
3) When uploading are the user defined fields still present even when the involved import file doesn't have data for the applicable field?

I think it's working now. I just did a quick import test. I'll test further.
Thanks - Henry

Quote:

---

Originally Posted by henry3

I think it's working now. I just did a quick import test. I'll test further.
Thanks - Henry

---

Glad that at least appears to have it working. Please do report test result/issues.

Quote:

---

Originally Posted by mc12345678

[So, here is what I understand in “date” order and therefore remain perplexed if there is an issue or not:
At point A a backup of the database was made.

At point B an export was made, the file modified to only include the primary reference key and user defined fields that were to be updated with whatever was in the import file.

At point C, the import file with the primary key and user defined data fields was imported causing the product identified by the primary key to be updated with whatever was present (or “absent”) in the user defined fields. The data for each field had been updated as desired/requested and all fields were present in the file. This included a field called products_ordered.

At point D (call it today), a comparison of the live database to the backup made at point A shows that everything is the same except for the data that was stored at point C. But the data in the products_ordered field is now zero instead of the quantity identified in the file at point C.

So question(s) are:
1) Did the import file at point C actually include the products_ordered field or not?
1.a) If it did, how do the values identified there relate to what is/was in the database?
2) If you were to again upload just a single row of data that included the products_ordered field and information for that field, what happens to the information of that product and field?
3) When uploading are the user defined fields still present even when the involved import file doesn't have data for the applicable field?

---

OK I just tested to confirm the issue and it DOES delete the products_ordered.

Here is want I did to test:

In phpmyadmin I modified the products_ordered for two items entering 100 for each. I saved and verified it was populated.
I then imported a csv file in EP, see below:

v_products_model,v_products_length,v_products_width,v_products_height,v_products _ready_to_ship,v_products_quantity
10,9.5,3.5,3.1,0,5289
20,9.5,3.5,3.1,0,5766

Import was successful but when I went back in phpmyadmin the products_ordered on both items were 0

So indication here is that if a user defined (custom) field is identified in the admin, then if the field is not included in the file it will be treated as being blank and therefore cleared of it's value. Further, until this issue is corrected it would be advised that a custom field not be listed in the admin field unless that field is to be modified by an import...

Quote:

---

Originally Posted by mc12345678

So indication here is that if a user defined (custom) field is identified in the admin, then if the field is not included in the file it will be treated as being blank and therefore cleared of it's value. Further, until this issue is corrected it would be advised that a custom field not be listed in the admin field unless that field is to be modified by an import...

---

Yes that seems to be the issue would you like me to test again BUT without the products_ordered field in admin?

Just tested again without the products_ordered in admin and it did NOT delete the products_ordered this time so yes confirmed that is the issue.

Quote:

---

Originally Posted by marcopolo

Yes that seems to be the issue would you like me to test again BUT without the products_ordered field in admin?

---

Quote:

---

Originally Posted by marcopolo

Just tested again without the products_ordered in admin and it did NOT delete the products_ordered this time so yes confirmed that is the issue.

---

Looking at a remnant of code in the import file it appears that I had begun adding the protection to prevent the issue you were experiencing. Looks like that needs to be completed/rectified still.

The goal being that the custom field could remain populated, but the data not cleared if the field is absent from the import file.

FYI, I believe I fixed the above problem, but still need to upload the changes to github... Wanted to run a couple more tests as well. Did find that the solution for the date/time issue was partially incomplete as I found cases of 0000-00-00 00:00:00 entered for the date_available related field instead of NULL, but at least it doesn't "seem" like it causes a problem by being there... Still to be incorporated/updated regardless of what it "seems". :)