lat9--sorry to bug you, but I had asked these questions awhile back and doesn't look like I ever got a clear answer. Would you be able to assist? Thank you for all you do!Quote:
Originally Posted by mcqueeneycoins
Printable View
lat9--sorry to bug you, but I had asked these questions awhile back and doesn't look like I ever got a clear answer. Would you be able to assist? Thank you for all you do!Quote:
Originally Posted by mcqueeneycoins
1) There's not a way to simply link a product to another category. You'd need a 2-line import, the first to change the product's master category to the linked one and the second to change the master category back.
2) What's the goal of what you're trying to do? Are you overwriting a specific product-id to reflect new product content or are you creating a new product with the same model number?
Ideally I would be able to overwrite the existing product id to reflect new product content, without having to use the remove command first. For example, replace and apple under the red category with a banana under the yellow category without creating a linked product (or leaving the apple product active). Or, even if I could just replace apple 1 with apple 2 in the same category, but with different model numbers, without creating a new product (or leaving the old product there) that would work too.Quote:
Originally Posted by lat9
I have 5,000+ products active at any given time, and the majority are unique single quantity items. Would just like to be able to clean up the database easily as they sell and replace them with new inventory. If it's not possible that's ok, just thought I'd ask.
Thanks again (any happy holidays!)
Granted, it's been a while since I've fussed with DbIo, but there's nothing I remember that prevents you from updating the model and content for a given v_products_id.
Just a side thought here.
reusing, deleting, and etc of database items can only result in problems.
A customer of 10+ years would have many items in their records that would not like having their data manipulated in such a manner.
With today's available storage, a few outdated db items hanging around should have little or no effect on operation.
IMHO, it's better for the customer to see "Sold Out" than "No Product Found".
"If it ain't broke, don't fix it"
lat9--unless I'm doing something wrong, even if I change product data in the csv file, it assigns it a new product ID on upload creating a new product and leaving the old product in place. Please let me know if there is a workaround I'm missing.
dbltoe--again, correct me if I'm wrong, but I am under the impression that a customer's order history will be saved based on the item they purchased at the time. If I update the product title, etc. I did not think that would also change the product information saved in their order history/data.Quote:
Originally Posted by dbltoe
My issue is that I'm adding ~500 products a month to replace items that sold. If I just keep adding new products, I'm having to scroll through hundreds of pages in my admin to make any changes. Unless I deactivate the products, my customers will be faced with the same issue--scrolling through hundreds of pages of sold out products just to find what they're looking for--not a user friendly experience. Even doing this with DBIO creates a cumbersome (and large) file that takes longer to upload/update and more potential for error in my opinion. What I am hoping to do is essentially replace old products with new, and update the "date added" field so customers see it as a new product, but without taking up extra database space and cleaning up old products in the process.
no, you are quite correct. customers detailed order data is stored in the orders_products table.Quote:
Originally Posted by mcqueeneycoins
you have a very real problem. that said, i'm not a fan of your solution. i would do modifications of the database select statement to present far less data to you. in that manner, one would not have to sort through hundreds of pages of sold out items on your admin pages. depending on what version of zc you are on would indicate where one might put said code. this is something i have done before...Quote:
My issue is that I'm adding ~500 products a month to replace items that sold. If I just keep adding new products, I'm having to scroll through hundreds of pages in my admin to make any changes. Unless I deactivate the products, my customers will be faced with the same issue--scrolling through hundreds of pages of sold out products just to find what they're looking for--not a user friendly experience. Even doing this with DBIO creates a cumbersome (and large) file that takes longer to upload/update and more potential for error in my opinion. What I am hoping to do is essentially replace old products with new, and update the "date added" field so customers see it as a new product, but without taking up extra database space and cleaning up old products in the process.
with regards to what to display to the customer, that is another tricky one that i have addressed with various solutions.
the potential problem you have, and perhaps something else could chime in, might be in some of your SEO implications in your suggested solution. depending on whether you have an URL rewriter, you may get penalized for duplicate content.
but there are more creative solutions to the problem of having a tremendous number of products in your products table.
that said, i have seen various manufacturers reuse UPN numbers; so it is not like what you are thinking about doing is unprecedented.
best.
Thanks, carl--using 1.5.8a at the moment. With an existing 1.5.4 site I have url rewriter and have been manually replacing products like what I describe above, but trying to be more efficient with the new 1.5.8a site I'm working on. At the end of the day, if the database product ID does not change, but everything else about the product is updated (model, name, price, etc.) AND url gets rewritten once updated, would this not be any different than creating a brand new product using a newer product ID? Customer order history is saved separate and can be recalled as needed. As long as I don't anticipate needing to reactivate an old product, I guess I'm failing to see the downside to what I'm proposing, but I'm not the expert and hence the reason I'm reaching out for advice. I just want to make sure if I execute on my plan using DBIO (assuming I can), I'm not overlooking something that will create problems.
Right now, when I update product information for a given product, including model, name, and category, what I hope will replace the old product with the new product just ends up creating a linked product. Is there a way to instruct DBIO to "move" the product rather than "link" it?
i do not use dbio so i can not comment on its use.
i was only commenting on your method of solving your problem.
best.
I just ran a quick Products update (using demo data) with the following CSVQuote:
Originally Posted by lat9
The model for product-id 1 was MG200MMS prior to that import; after the import it was MG200MMS-updated.Code:v_products_id,v_products_model,v_products_quantity,v_dbio_command
1,MG200MMS-updated,28,