OBJECTIVE
I have imported over 2,000 products in a BV5 store using the BV Import tool that does not support the import of shared choices.
I have defined 8 Shared Choice fields using "Catalog - Shared Choices".
I need to add the 8 shared choice fields to each of the 2,000+ products.
This will take weeks if done manually. I would like to add the choice fields programmatically. I thought I could write a sile stored procedure that would populate bvc_ProductXInput with one entry per product/choice comibination.


ASSUMPTION
The 8 shared choice fields are stored in bvc_productinputs without a productID
I used the admin user interface to edit a product and added a shared choice usiing the Product Choices page.
An entry was made in bvc_ProductXInput which includes bvc_product.bvin, bvc_productinputs.bvin, and a date

I assume, therefore, that I can use a stored procedure to add product choices by populating the bvc_ProductXInput table with the appropriate pairs of bvins for products and shared choice fields



PROBLEM
When I manually populated bvc_ProductXInput with a bvin from bvc_product and a bvin from bvc_productinputs along with a date, the manually entered choice field was not visible in either the admin view of the product choices for the product or the store view of the choices for the product. Other choice fields entered using the admin user interface are visible.



THe attached gif file illustrates the table entries in question.



When I run a simple query to verify the links between the productxinput and the productinputs tables the manually populated choice fieled is picked up.



What am I missing?



Thanks!

-bob

I am puzzled. I deleted all choices for the test product. I then added a choice using the sql interface. Unlike the last time, I found the choice displayed as I would expect in both the admin and store-front user interfaces. Not sure what I did differently.
Regards,

-bob