Greetings All:


Need some info on how to best proceed in updating cross-sell and upsell product options. Due to the size of our catalog, it is virtually impossible to do our maintenance using admin web interface. What we have been doing going back to BVC2004 is doing direct SQL updates to the BV SQL Server database. W still do this with BV5 with relative success. In BV5, most index fields use some hashed value. In the case of the product upsell and crosssell tables, these are generated when a cross-sell or upsell item is created for a product. I am not sure if it is referenced by any other table like the product SKU would be. We were able to do a batch update with SQL statements and imported tables but this process involves creating several dummy rows for the table using the bvadmin web interface and then updating the rows created with SQL statements. In other words, we create rows first using the BVadmin to get the program to generate the hashed values for each row and then updating it with the SKUs we want.



In short, the question is:



1) for the cross-sell and the upsell tables are the hashed values necessary...can we just add to rows to those table using unique but pre-defined values using SQL append statements.

2) if the answer to number 1 above is that the hash value has to be generated, can hashed values be created outside the web interface.



Thanks.



Nolan

Is there a way to have crosssells rotate from an 'approved' list or load at random?

It would be helpful to build a crosssell category populated only with crosssell-worthy products.

Adding a product and adding it to a few others as crosssells is getting to be a lot of work.