Uploading Product Attribute Option Values ?

Hi Everyone,

         I recently installed Zencart V 1.5.0.

My website has around 950 products and around 380 Attribute Option Values.

I do not want to add these option values manually. I installed "Easy Populate 4.0.19 - Beta 1-28-2012" as well as "APSONA ShopAdmin" to bulk upload Option Values, but none of these products are helping me.

So my question is, Can I directly upload "Option Values" to this table "products_options_values" in the database, using a SQL Script without messing the Database ?

Will there be any side-effects ? Do I need to update any other table as well ?

Once I am done uploading "option values", I plan to use Apsona's Product attributes: import/upload tool to link Products with "Attribute Option Values".

Plz advise.

Many Thanks

You have to have Option NAMES first, before you can assign or configure Option VALUES.

schoolboy:

You have to have Option NAMES first, before you can assign or configure Option VALUES.

Yes, I already added the "Option NAMES" from the Admin Panel.

So is it ok now, if I simply add "Option VALUES" to this table "products_options_values" using a SQL Insert script ?

Alright, Over 85 views, still no answer.

Anyway, I just went ahead and added almost 485 option values to the "products_options_values" table using SQL Script. Then used Apsona's shopadmin to link products to attributes (option values).

I also had to set the "Sort Order", because products are priced by attributes, and I want to show the prices in ascending order. This is very important, otherwise, I think the attributes will show up in a random order.

Here is a screenshot after I uploaded my values. As you can see, My SKUs were based on attributes.

Here is a screenshot of one of the pages with attributes that I uploaded....

So far so good ..... :smile:

Hope my experience with bulk option values uploading helps someone else.

Rony:

Alright, Over 85 views, still no answer.

Anyway, I just went ahead and added almost 485 option values to the "products_options_values" table using SQL Script. Then used Apsona's shopadmin to link products to attributes (option values).

I also had to set the "Sort Order", because products are priced by attributes, and I want to show the prices in ascending order. This is very important, otherwise, I think the attributes will show up in a random order.

Here is a screenshot after I uploaded my values. As you can see, My SKUs were based on attributes.

Here is a screenshot of one of the pages with attributes that I uploaded....

So far so good ..... :smile:

Hope my experience with bulk option values uploading helps someone else.

Option VALUES are associated with their Option NAMES in the database via a complex relational cross-reference, governed in products_options_values_to_products_options. I trust you remembered to assimilate all the Option NAME ID's with their corresponding Option VALUE ID's, and that you wrote the relevant data to this table as well?

Below (and sorry about the length) is one of MY database's relatively simple relational data

(`products_options_values_to_products_options_id`, `products_options_id`, `products_options_values_id`) VALUES
(1, 1, 1),
(2, 1, 2),
(3, 1, 3),
(4, 2, 4),
(5, 2, 5),
(6, 2, 6),
(7, 2, 7),
(8, 2, 8),
(9, 2, 9),
(10, 2, 10),
(11, 1, 11),
(12, 3, 12),
(13, 3, 13),
(14, 3, 14),
(15, 1, 15),
(16, 1, 16),
(17, 1, 17),
(18, 4, 18),
(19, 4, 19),
(20, 4, 20),
(21, 4, 21),
(22, 4, 22),
(23, 4, 23),
(24, 5, 24),
(25, 5, 25),
(26, 5, 26),
(27, 4, 27),
(28, 5, 28),
(29, 4, 29),
(30, 4, 30),
(31, 4, 31),
(32, 6, 32),
(33, 6, 33),
(34, 6, 34),
(35, 1, 35),
(36, 2, 36),
(37, 2, 37),
(38, 2, 38),
(39, 2, 39),
(40, 2, 40),
(41, 2, 41),
(42, 2, 42),
(43, 2, 43),
(44, 2, 44),
(45, 2, 45),
(46, 2, 46),
(47, 1, 47),
(48, 1, 48),
(49, 7, 49),
(50, 7, 50),
(51, 7, 51),
(52, 8, 52),
(53, 8, 53),
(54, 8, 54),
(55, 8, 55),
(56, 1, 56),
(57, 1, 57),
(58, 9, 58),
(59, 9, 59),
(60, 9, 60),
(61, 10, 61),
(62, 10, 62),
(63, 10, 63),
(64, 10, 64),
(65, 10, 65),
(66, 10, 66),
(67, 10, 67),
(68, 10, 68),
(69, 1, 69),
(70, 1, 70),
(71, 1, 71),
(72, 1, 72),
(73, 1, 73),
(74, 1, 74),
(75, 1, 75),
(76, 4, 76),
(77, 4, 77),
(78, 4, 78),
(79, 11, 79),
(80, 11, 80),
(81, 11, 81),
(82, 11, 82),
(83, 11, 83),
(84, 11, 84),
(85, 12, 85),
(86, 12, 86),
(87, 12, 87),
(88, 12, 88),
(89, 12, 89),
(90, 10, 90),
(91, 10, 91),
(92, 10, 92),
(93, 13, 93),
(94, 13, 94),
(95, 13, 95),
(96, 13, 96),
(97, 2, 97),
(98, 2, 98),
(99, 2, 99),
(100, 2, 100),
(101, 2, 101),
(102, 2, 102),
(103, 2, 103),
(104, 2, 104),
(105, 2, 105),
(106, 2, 106),
(107, 2, 107),
(108, 2, 108),
(109, 2, 109),
(110, 2, 110),
(111, 2, 111),
(112, 2, 112),
(113, 2, 113),
(114, 2, 114),
(115, 2, 115),
(116, 2, 116),
(117, 2, 117),
(118, 2, 118),
(119, 2, 119),
(120, 2, 120),
(121, 2, 121),
(122, 2, 122),
(123, 2, 123),
(124, 2, 124),
(125, 2, 125),
(126, 2, 126),
(127, 2, 127),
(128, 2, 128),
(129, 2, 129),
(130, 2, 130),
(131, 2, 131),
(132, 2, 132),
(133, 14, 133),
(134, 14, 134),
(135, 14, 135),
(136, 14, 136),
(137, 14, 137),
(138, 15, 138),
(139, 15, 139),
(140, 15, 140),
(141, 15, 141),
(142, 15, 142),
(143, 16, 143),
(144, 16, 144),
(145, 16, 145),
(146, 2, 146),
(147, 2, 147),
(148, 2, 148),
(149, 2, 149),
(150, 2, 150),
(151, 2, 151),
(152, 2, 152),
(153, 4, 153),
(154, 2, 154),
(155, 2, 155),
(156, 2, 156),
(157, 2, 157),
(158, 2, 158),
(159, 2, 159),
(160, 2, 160),
(161, 2, 161),
(162, 14, 162),
(163, 17, 163),
(164, 17, 164),
(165, 17, 165),
(166, 17, 166),
(167, 15, 167),
(168, 14, 168),
(169, 14, 169),
(170, 2, 170),
(171, 2, 171),
(172, 2, 172),
(173, 2, 173),
(174, 16, 174),
(175, 16, 175),
(176, 16, 176),
(177, 16, 177),
(178, 16, 178),
(179, 16, 179),
(180, 3, 180),
(181, 18, 181),
(182, 18, 182),
(184, 18, 183),
(185, 4, 184),
(186, 4, 185),
(187, 4, 186),
(188, 4, 187),
(190, 12, 188),
(191, 12, 189),
(192, 4, 190),
(193, 18, 191),
(194, 1, 192),
(195, 4, 193),
(196, 19, 194),
(197, 19, 195),
(198, 19, 196),
(199, 2, 197),
(200, 2, 198),
(201, 2, 199),
(202, 2, 200),
(203, 2, 201),
(204, 2, 202),
(205, 2, 203),
(206, 2, 204),
(207, 2, 205),
(208, 2, 206),
(209, 2, 207),
(210, 2, 208),
(211, 2, 209),
(212, 2, 210),
(213, 2, 211),
(214, 2, 212),
(215, 2, 213),
(216, 2, 214),
(217, 2, 215),
(218, 2, 216),
(219, 2, 217),
(220, 2, 218),
(221, 2, 219),
(222, 2, 220),
(223, 2, 221),
(224, 2, 222),
(225, 2, 223),
(226, 2, 224),
(227, 2, 225),
(228, 2, 226),
(229, 2, 227),
(230, 2, 228),
(231, 20, 229),
(232, 20, 230),
(233, 20, 231),
(234, 20, 232),
(235, 20, 233),
(236, 20, 234),
(237, 19, 235),
(238, 5, 236),
(239, 5, 237),
(240, 5, 238),
(241, 5, 239),
(242, 5, 240),
(243, 5, 241),
(244, 17, 242),
(248, 17, 244),
(247, 17, 243),
(249, 17, 245),
(250, 17, 246),
(251, 17, 247),
(252, 14, 248),
(253, 14, 249),
(254, 14, 250),
(255, 14, 251);

schoolboy:

Option VALUES are associated with their Option NAMES in the database via a complex relational cross-reference, governed in products_options_values_to_products_options. I trust you remembered to assimilate all the Option NAME ID's with their corresponding Option VALUE ID's, and that you wrote the relevant data to this table as well?

I think that part is handled by Apsona ShopAdmin Module which I used to link products to attributes (Option Name as well as Option Values). Bcoz, when you upload, it ask you to provide

• Product Name,
• Option Name,
• Option Value &
• Option Price

There are some other fields as well that you can specify, but I didn't used all.

All my Product Names are unique, I even used Unique Option Values bcoz I generate my SKUs with them.

So far I don't see any errors anywhere, hope it has been taken cared of by Apsona properly.

Rony:

hope it has been taken cared of by Apsona properly.

Undertaking a critical procedure, basing it on "hope" is not very professional.

I don't think you understand what the products_options_values_to_products_options_id table does.

Or if you do, you seem to be casually ignoring its importance.

schoolboy:

Undertaking a critical procedure, basing it on "hope" is not very professional.

I don't think you understand what the products_options_values_to_products_options_id table does.

Or if you do, you seem to be casually ignoring its importance.

Yes, Exactly, I DO NOT understand Zencart internal complex database relationships. That's why I came here to seek advise, but when I didn't received any, I had to start experimenting myself. I thought it was better to jump in and get hands dirty in the code than sitting idle for days/weeks hoping that someday someone may give me an expert advise.

I know there are issues with experimenting.

But uploading almost 500 option values (& more coming) manually just isn't practical.

It is unlikely that you will now be able to add attributes properly via the admin interface, and if you try, it will probably cause some significant conflicts - many of which may not be immediately visible.

That RELATIONAL TABLE is critical to the proper functioning of attribute option names to their associated values.

Also... to UNDO what you have done (the best option) is not going to be easy.

I trust you made a backup of your database before you "experimented"? You would do well to restore that backup.

Four months ago we had to load up 16,000 products to a client's database, all with complex attributes (several hundred of them). Following the tutorials at Apsona, we created SEVERAL spreadsheets, and then used apsona to do the work.

Took a few hours, but with care, and attention to detail, it got done.

Yup, I messed up the Database ..... But no worries, my site is not LIVE .... I can wipe out the database and start all over again.

But this time I am first reading and trying to understand this ....

http://upload.wikimedia.org/wikipedia/commons/f/f6/ZenCart_DB_Schema.jpg

before doing any bulk uploading ....

ZenCart is in the market for almost a decade now, I can't believe why so far nobody built a good, easy to use add-on for bulk attribute uploading, including option names and option values. :dontgetit

"ZenCart is in the market for almost a decade now, I can't believe why so far nobody built a good, easy to use add-on for bulk attribute uploading, including option names and option values."

Every store is unique with regard to attributes. Your attributes are unlikely to be the same as anybody else's - so it is not possible to configure a system that universally applies to everybody.

Apsona comes close to providing a mechanism to load attributes as quickly as possible, requiring that you provide your data in a delimited file (csv spreadsheet).

As it is far quicker to use spreadsheets to compile this data (rather than the one-by-one facility in zencart), loading attributes is virtually instant once this spreadsheet is configured.

That is what I used last time ..... APSONA .....It didn't inserted any rows in this table .... products_options_values_to_products_options

I followed all the instructions here http://apsona.com/doc/import-upload-attributes-into-zen-cart-or-oscommerce

But it didn't worked ..... Doing it all over again now ....

I think this is what I did wrong last time ..... I used EP to upload products and then used Apsona to upload attributes ....

This time I am gonna use Apsona from start till end.

Has there been any kind of update to this recently ??

I too have the same set up as the "OP" **zen cart 1.50 "Easy Populate 4.0.19 - Beta 1-28-2012" as well as "APSONA ShopAdmin" **

I have products to upload, but altogether these have over 27500 attributes,

Trying this manually "one by one" is a nightmare ,,,,

Hi i have a headache!!!

I am trying to upload product attribute values (See Picture) To start with i uploaded the products (With Price) But when i added the attributes , The (Start At:) Price went blank, Not Good, But the effect was good, I chose a size and it added it to shopping cart at the attributed price,,

As i need it show (Start At:) Price AND give me the correct attribute when selected, It won't do it !!!!

If i show the price it adds it to the selected attribute, It will ADD the price onto the attribute price,

If i don't show the price it will add it correctly ,

I really need both to work together????

Please note: The price you see on the attached is the kind of problem i have if i upload the product price and attribute together..

This is the original way i had this, this sequence "Still" adds the starting at price along with attributed price, Seems if i have more than one Size-Price attribute category, It doesn't know what to do with it, Or probably i don't :no:

Is it possible to do a parent product and canonicalise up to the parent product,??? As i realise/was told this way won't work, and would have to clone the product ?

Is parent - canonical possible ?