Database I/O Manager (DbIo) Plugin [Support Thread]

[Ryk]

Hi Cindy

Thanks for that rapid response. So just using the 3 columns is OK - darn it! Hate it when the customer is right LOL

Can you explain though why allow duplicate models on import should be set when removing a product? He's bound to ask, so I may as well give him the corrrect answer rather than something I made up!

Thanks

Ryk

[lat9]

Hi Cindy

Thanks for that rapid response. So just using the 3 columns is OK - darn it! Hate it when the customer is right LOL

Can you explain though why allow duplicate models on import should be set when removing a product? He's bound to ask, so I may as well give him the corrrect answer rather than something I made up!

Thanks

Ryk

It depends on how the customer intends to perform the removal. If he's going to just list the v_products_id values to be removed and leave the v_products_model field blank, the REMOVE operation will fail since the duplicate-model checks occur prior to the determination that the request is a product removal.

[Ryk]

Many thanks

[Hasher]

Does anyone know what this error is related too ?

✗ Product not inserted at line number 488; category id (613) has categories.
✗ Product not inserted at line number 489; category id (613) has categories.
✗ Product not inserted at line number 490; category id (613) has categories.

Other Products in the same category import correctly.

Thank in advance !

[lat9]

Does anyone know what this error is related too ?



Other Products in the same category import correctly.

Thank in advance !

Could you post one of the CSV lines that imports correctly and one that doesn't for that category #613?

[Hasher]

Could you post one of the CSV lines that imports correctly and one that doesn't for that category #613?

Hi Lat9

Attached a file , First line imports fine but next 3 lines are the problem

https://yadi.sk/d/ahtSFAF_KFri8w

Hope this helps. :)

[lat9]

Hi Lat9

Attached a file , First line imports fine but next 3 lines are the problem

https://yadi.sk/d/ahtSFAF_KFri8w

Hope this helps. :)

... and it did! The first line identifies a category-path of Agriculture^Tractors^Challenger^MT 400 B^

and the subsequent lines identify a category-path of Agriculture^Tractors^Challenger

Upon importing that first product, the Agriculture^Tractors^Challenger category now has a sub-category (MT 400 B), so products can't be added to that 'parent' category.

[Hasher]

... and it did! The first line identifies a category-path of Agriculture^Tractors^Challenger^MT 400 B^

and the subsequent lines identify a category-path of Agriculture^Tractors^Challenger

Upon importing that first product, the Agriculture^Tractors^Challenger category now has a sub-category (MT 400 B), so products can't be added to that 'parent' category.

Thank you Lat9 ,

You save me everytime !

[RixStix]

Thanks lat9,

DBIO saved a tremendous amount of time reconfiguring attribute switches that were affected by some attribute pricing changes made in 156 from 154

Export the table, edit it in Excell and upload..... whew

[lat9]

Thanks lat9,

DBIO saved a tremendous amount of time reconfiguring attribute switches that were affected by some attribute pricing changes made in 156 from 154

Export the table, edit it in Excell and upload..... whew

No problems, @RixStix, I'm happy that DbIo was helpful. For my edification, which attribute-pricing changes were causing you grief?