Bug: Filtering issue in SuiteCRM 8.9.3

fo1 · 25 March 2026 17:06

In SuiteCRM version 8.9.3, there is a bug in the filtering functionality.

Steps to Reproduce

Go to the official SuiteCRM demo page: SuiteCRM
Open a module with list filtering, for example Opportunities
Click Filter in the top right corner
Select a filter value, for example Sales Stage = Prospecting
Click Search
Notice that the results are not filtered correctly
Open the filter panel again
The selected filter value is now displayed as “null”

Expected Behavior
The selected filter should be applied correctly, and the chosen filter value should remain visible in the filter field.

Actual Behavior
The filter is not applied correctly, and the selected value is replaced with null.

Request
Could you please investigate and fix this issue in an upcoming release?
If a workaround already exists, I would appreciate it if you could share it as well.

rsp · 25 March 2026 18:16

Thank you for raising an issue on the GitHub:

github.com/SuiteCRM/SuiteCRM-Core

Multiselect fields (Core & Custom) return null/empty strings on partial selection in SuiteCRM 8.9.3

opened 05:13PM - 25 Mar 26 UTC

kingfisher77

Type: Bug

### Issue In SuiteCRM 8.9.3, Multiselect fields (both Core fields and Custom mu…ltienum fields) do not function correctly in the new Angular frontend (EditView and Filters). While "Select All" works and saves correctly, selecting only a few items results in empty values (^^,^^) being saved to the database and null values being displayed in the UI. ### Possible Fix ? ### Steps to Reproduce the Issue ```bash 1. Create or use a Multiselect field (e.g., Lawful basis in Contacts). 2. Open the Contact in the new SuiteCRM 8 EditView. 3. Select only 2 or 3 items from the dropdown (do NOT select all). 4. Save the record. Observe that the UI shows "null" or empty values, and the database contains empty carets (e.g., ^^,^^,^^) instead of the keys. Partial selections should be mapped correctly to their keys and saved as ^key1^,^key2^. ``` ### Context Legacy Mode: Works perfectly (data is saved and displayed correctly). New Frontend: Sending empty strings for selected indices. Browser Inspect: The GraphQL response/payload shows [null, null] for the field state. ### Version 8.9.3 ### What browser are you currently using? Chrome ### Browser Version Latest Chrome ### Environment Information MariaDB, PHP 8.2 ### Operating System and Version Docker (official php:8.2-apache base)