The Challenge: An Unsortable Column

Tables often display calculated fields, such as "Days Open," which is derived from the difference between a start and end date using a response data transform of a data page. While the calculated value appears correctly in the table column, users are unable to sort the table based on this "Days Open" column. The sorting function simply does not work for this calculated field.

The primary question is: Why isn’t sorting applied to this calculated field when it comes from a data page populated via a response data transform?

The "Why": Understanding the Behavior

When a property is populated from the response data transform of a data page, it is created during the data page's execution. This means the property and its value exist in memory and not in the database.

The sorting mechanism for tables is designed to operate on database values. Since the calculated property does not have a corresponding value in the database, the sort operation fails.

Recommended Approach ✅

With the release of Infinity '25, there is now enhanced support for calculations directly within insights. You can leverage this new calculation feature to compute the value for fields like "Days Open."

This is the recommended method for adding calculated fields to insight tables. By using this feature, you will also gain support for other critical functionalities such as:

By adopting this new approach, you can ensure that your calculated fields are fully functional and provide a better user experience.

References:

Creating a calculated field

Specifying custom calculations

Constellation 101 Series 

Enjoyed this article? See more similar articles in Constellation 101 series.