Developer forum

On your second screendump where you show variantgrouproductrelation, you have a sort column that contains 0 for both - you need to give them sort values 1 and 2 respectively.

BR Nicolai

Dear Nicolai,

Appreciate for your respond.

We will try it out and let you know.

I am just curious that is it the new field which had added on latest version of Dynamicweb?

Thanks,

Yoon

Dear Support,

We followed your solution on 21/12/2022. However, we are continuing to encounter the issue with the variant products. The system still tries to generate the sequence of the variant wrongly. 

The error message is still being displayed for the product, even though it was created with the correct sequence number in the table.

Despite following your suggestion to sort the variants with numbers 1 and 2, the problem persists. 

 Please find the working product below for your reference.

We are seeking your guidance and advice on this matter as soon as possible.

Thank you.

Best Regards,

Yamin

Hi Yamin

Please see this thread: https://doc.dynamicweb.com/forum/ecommerce-standard-features/ecommerce-standard-features/wrong-order-of-variant-combinations-on-product

There is actually a link to a test version of a dll that I think will solve the issue in your case as it will sort the groups depending on the sortorder and the autoid and not rely on a database index.

You can however, as also mentioned in the above thread, create a database index (described in the post as well) that will fix the sorting issue.

We are currently working on a permanent solution

BR Nicolai

Dear Nicolai,

Thank you for your response. We have attempted the method you suggested; however, it did not resolve our particular issue. We are eagerly awaiting your further assistance and would appreciate knowing if you have any other solutions to offer. Could you please provide us with an update on the progress toward a permanent solution?

Best regards,

Yamin

Dear Nicolai,

May I get any feedback on this? Thanks.

Best regards,

Yamin

Hi Yamin,

What was the result of using the dll that Nicolai mentioned?  That seems to be the permanent fix.