Sorting getResources by an Integer TV Value in Evolution CMS

Sorting by a TV only becomes reliable once the snippet knows what type of value it is handling. If a numeric field such as area is sorted as plain text, the result order will look wrong even though the query technically works.

The original question came down to this: which parameter tells getResources to treat the TV as an integer instead of a string? That is the right question, because numeric sorting is a data-type problem, not a template problem.

This is a classic catalog issue on Evolution CMS projects. Fields like area, price, weight, rating, or stock often live in TVs, and the listing layer needs explicit numeric semantics to sort them correctly.

Whenever a TV-based sort looks “almost right but strangely shuffled”, type handling should be the first thing you inspect.