Number Fields in Studio Do Not Support Range Search in SuiteCRM Version 8.6.2

[aooppo]

Issue

In SuiteCRM Version 8.6.2, when configuring a number-type field (e.g., integer or float) in Studio to support range searches, the search filter in the list view does not display a range input control. Instead, it remains a single input field that only allows the entry of a single number. This makes it impossible to perform range-based searches on numeric fields.

This issue limits the usability of numeric fields where filtering by a range is essential (e.g., filtering by values between a minimum and maximum).

Possible Fix

This may require changes to the front-end filter logic to allow numeric fields to support range inputs, similar to how date range filters are implemented.

Steps to Reproduce the Issue

1.	Navigate to Admin > Studio in SuiteCRM.
2.	Select any module (e.g., Accounts, Opportunities).
3.	Create or edit a field of type Number (e.g., Integer, Float).
4.	In the field configuration, check the Enable Range Search checkbox and save.
5.	Deploy the changes.
6.	Go to the list view of the selected module and open the search filter.
7.	Attempt to perform a range search (e.g., search for values between 10 and 100).

Context

This issue prevents users from performing range-based searches for numeric fields, which is critical in scenarios like filtering records by revenue, quantity, or other numerical metrics.

Version

SuiteCRM 8.6.2

What browser are you currently using?

Chrome

Browser Version

Chrome Version 131.0.6778.265

Environment Information

Ubuntu 20.04, PHP 8.0 MariaDB

Operating System and Version

Ubuntu 20.04

[johnM2401]

Hey!
Thank you for getting in touch!

I believe this issue may have been resolved in the 8.7.0 Release.
I've given this a try on the most recent version, (8.7.1), and it appears as though Ranged Searching is working as expected:

Would it be possible to try this on a more recent version of SuiteCRM?
(or the Suite8 Demo: https://suite8demo.suiteondemand.com/ )

And let us know if you are still experiencing this issue?

If so, I would be happy to investigate!

Thank you again!