Developer forum

Forum » Ecommerce - Standard features » Variants data seem to get corrupted

Variants data seem to get corrupted

Ton Martens
Reply

Variants-data seems to get corrupted although data has never been saved

A product has several variants (afmetingen tafelbladen). Within the product overview, the variants can be shown by clicking the '+' which unfolds the variants. 
On the product detail screen, clicking the "Variants" button (not the arrow!), we get an overview of variants.

All fine so far.

Now, by clicking the Variants button's arrow-down, all variantgroups appear with green checkmarks. One by one I clicked these checkmarks, expecting to get a view of variants. I expected the first one to give me an overview with active variants (because they are there), and I expected the other two checkmarks to give me an empty result. However, after checking all three checkmarks, I was confused of the results and clicked 'close' at the product-ribbon, in order to cancel my actions. I never clicked 'Save'.

This brings me back at the product overview. Now, clicking the '+' at that product, I get a .Net error. Also, going into the product detail screen and clicking the "variants" button, does not give me the original variants overview anymore.

This happens in 8.4.1.23, but my collegea (Ben) confirmed that this problem also existst in the latest version.

1. A .Net error should never occur. Customers get very frustrated by these kind of screens; 
2. It should not be possible to 'corrupt' or alter data without even click a 'save' button.
3. It's not clear what the intented functionality of the "variants"-button is (clicking the arrow-down at the right side of the button). 
4. At the end of these actions, all variant groups have been selected for the product, none of these are active. The initial variants don't show up in the backend anymore.

Thanks,
Ton

DwVariantProblem.png

Replies

 
Nicolai Høeg Pedersen
Reply

Hi Ton

We need a link to the solution to see what have happened.

This does not happen on new version - and Ben has not checked because variant management is completely redone in 8.5 and looks totally different.... wink

The reason the UI was changed was your points 2-4. Of course exceptions should not be able to occur - I'm sure this has been fixed in new versions.

 
Adrian Ursu
Reply

Hi Guys,

We have also experienced some issues with variants in 8.6. Reported it to Support. It was clasified as "ghost"

In our case the variants that were created before 8.6 were not visible in the front-end although they seemed ok in the back-end. Analysis of table data did not show anything out of the ordinary. New variants have been displayed without problems. Copies of old variants/products were also displayed correctly.

If you care to look, the solution is sym.dotfusion.ro.

Thanks,

Adrian

 
Ben Doorn
Reply

Hi Nicolai,

Indeed the new version (8.6.0.0, I will retry with 8.6.0.4) has a redesigned interface, but the problems with the data still exist. When adding a variant group and not saving the data results in an error on the list page, I assume when adding a group the record is immediately added to the database table and when the product is not saved the database gets in an unexpected state resulting in the .net error message.

The second thing I noticed was that adding a new group deletes all existing variants (i have to recheck if this was before or also after i saved the data), which seems logical the way the variants are managed from a technical point of view, however the avarage user does not understand what is happening. We realy need to improve this. Please let me know if you want extra input from us to resolve this.

Kind regards,

Ben

 
Nicolai Høeg Pedersen
Reply

Hi Ben

Will check the exception.

If you add another dimension to a product, all existing variants are deleted. Because you can not have a "red" only if color is also on your matrix. So if you have the color variant group already and added 3 colors, then when adding the size group - what sizes should the existing colors be? That would also be confusing...

 
Nicolai Høeg Pedersen
Reply

Hi Adrian

Your problem seems to be different.

@Ben - I cannot reproduce this on my solutions. Can you provide a URL?

 
Ben Doorn
Reply

Hi Nicolai,

I rechecked with 8.6.0.4. In that version the .Net error seems to be fixed. I used a wrap solution om my local system to test.

About the configuration interface, as I mentioned it is logical from a technical point of view that your existing variants are deleted when adding a new group (dimension). But removing the group then does not restore the previous configuration. Wouldn't it be better to warn the user that this is going to happen.

Kind regards,

Ben

 
Ton Martens
Reply

"...and Ben has not checked because.."

tss tss tss

 
Nicolai Høeg Pedersen
Reply

@Ben

It does warn that the current combinations are deleted. And we have to clean the data when variant groups are changing.

 

You must be logged in to post in the forum