Resolved "multi_variant" fields vs "custom" fields

Hello Vittorio,

so first question is: can I use "multi_variant" fields?

Yes, you can.

I don't know if beta 3 Pro is more or less updated than 6.1.2..

The beta 3 version is older than the 6.1.2 version. Simply put 6.1.2 is newer than beta 3.

if I can use multi_variant fields, which is the difference with respect to "old" custom_title, custom_param, custom_value fields?

There is no "old" custom fields import. The custom_title, custom_param and custom_value fields are still used for importing custom fields. The difference is that the multi-variant is such a special custom field it requires special coding and a special way of importing.

Which are preferrable?

It is not that one is better than the other, it depends on which custom field you decide to use. The Multi-Variants is a custom field with a specific use-case.

Hello,
I started working with multi-variant custom fields, trying to figure out how to handle relative CSVI fields. I read another discussion about this in the forum, I worked trying to follow that but I still have some troubles.
I created a multi-variant custom field on VM3, named "size". I would like to have just one ramification and to use custom labels (not product names). Now, it's not clear to me what I have to put in both multi_variant_fields and multi_variant_title fields.
Shall I create another custom field (string type) named "options" for instance, and then configure multi_variant_title = "size", multi_variant_fields = "options" for father products and then size = "shirt S", "shirt M",etc for child products?
I tried this way but I cannot see any dropdown menu on frontend side..consider that I have already updated available fields and I see "size" on fields list.
I tried also to manually create a VM product in order to perform an export and to see fields' values; however I found that fields like multi_variant_title and multi_variant_fields are not available for CSVI export..

Hi Roland,
I try to give you some files/images in order to let you understand my concerns for importing a csv file with multi_variant fields.
In file "expected.jpg" you can see the goal: the product has been created manually on VM3. As you can see, the multi_variant custom field is "Taglia" (it means size) and the custom label for the unique ramification is "Taglia_custom". I noticed that, once updated available fields in manteinance menu, only the custom label "taglia_custom" is available as a custom field (see available_fields_updated.jpg). So one of my concerns is: where is custom field "taglia" used?
By the way, "my_csv_file.csv" is csv file that I use for the import. It contains multi_variant_fields, multi_variant_title and Taglia_custom columns. As far as I understood, fields like "custom_value", "custom_title", "custom_param" and so on cannot be used for my purpose.
When I import this file, I cannot see the dropdown menu on frontend and in backend I see "result.jpg". Taglia_custom is not visible and furthermore I lose the choice of the father custom label in the children list.
I don't know if an important role is represented by the configuration/creation of the multi variant custom field in VM3. I mean, shall a string custom field be created, then associated to the multi_variant custom field (see custom_fields.jpg)? If so, how shall I use it? And do you know if the following 3 "internal variables" have to be set to "yes" instead?

Thank you

Vittorio

Hello Vittorio,

So one of my concerns is: where is custom field "taglia" used?

Taglia is not a custom field for CSVI because it is a Multi-Variant field and therefore it is a special field. It is used by the multi_variant_title field only.

The field Taglia_custom in your CSV file must not be Alcott Jeans Pink Taglia 24 but should be Camicia XS

As far as I understood, fields like "custom_value", "custom_title", "custom_param" and so on cannot be used for my purpose.

You can use them but not for the multi-variant fields.

I mean, shall a string custom field be created, then associated to the multi_variant custom field (see custom_fields.jpg)?

That is not necessary.

And do you know if the following 3 "internal variables" have to be set to "yes" instead?

I was told to ignore these fields by the VM team.

After import the field for the label should be set to Usa etichetta ... but I see it didn't happen in your case. Make the suggested changes and run the import to collect the debug information as well. Check the result. If it is not good please post the debug log and file and I can check what is happening.

Hi Roland,
thank you for the explanation.
"Camicia XS" and "Alcott...." are different products: first one was created manually by me, second one was created just for import. This is why I did not use "Camicia XS" in the import file.
By the way, I tried to use both "Camicia XS" and "alcott..." in the Taglia_custom field: unfortunately the result is the same as the one described in my last post.
I'm attaching the debug file as requested (here I used "camicia xs" taglia_custom value for the import).

Thanks
Vittorio

Hello Vittorio,

Now with the debug log I was able to identify the issue and fix it. Attached is a patch file that you can load. After that the import should be working as expected.

Please let me know how it goes.

Hi Roland,
now it works as expected! Thank you for the patch!

Regards
Vittorio

Hello Vittorio,

Thank you for the feedback.