Developer forum

Forum » CMS - Standard features » Product Category Fields Sort Order

Product Category Fields Sort Order

Steve Knutson
Reply

Hi Everyone,

We've been using the Product Category for our dynamic web solution and each of the product categories contains a large number of fields.

When editing the Product Category you can specify the sort order of the Fields. However, each time when our app service is restarted, the fields in each of our Product Categories are reordered alphabetically and not in the order we specified earlier.

 


Replies

 
Morten Snedker Dynamicweb Employee
Morten Snedker
Reply

Hi Steve,

Is the structure of your categories and their fields maintained in UI only?

Because if it happens as you describe, it is indeed very strange. As you can see in this screencast, I have not been able to reproduce the scenario you have described. When you perform the sorting, the value of the sort order is saved to database. And I do not see how these values (sustained in database) should be altered by an application recycle.

Can you think of anything that would change these data (import job, update from Visual Studio repository or alike)?

BR
Snedker

 
Steve Knutson
Reply

Hi Morten,

Here is a screencast showing the issue we are facing. I have noticed that you are using the DynamicWeb version 9.13 and it has a different UI for sorting the fields i.e. the 9.13 version has a sort button on the top toolbar whereas the version we are using is 9.10.10 where you can drag individual fields to sort them as shown in the screencast. In the screencast, you will notice that the DynamiceWeb instance is not respecting the FiledSortOrder value stored in the database after we recycle the App pool.

Regards,

Steve

 
Morten Snedker Dynamicweb Employee
Morten Snedker
Reply
This post has been marked as an answer

Hi Steve,

Ah, yes I see the problem. Reviewing our backlog I can see that this was reported as a bug late last year, and that it was resolved with the current functionality (own window for sorting) early March this year. So the solution is an upgrade to 9.13 where this is fixed.

BR
Snedker

Votes for this answer: 1

 

You must be logged in to post in the forum