Report Module not able to save empty criteria or conditions fields "none" or "null"

📦 Install & Upgrade Help
1

since 7.11.17 update I have occur the following in the report Module, but do be honest I’m not fully sure if it has to do with the update.

In Report Module: if edit an Report and choose for an field “none” or “empty” it would be overwritten after saves to an different value. The mysql would not show “NULL” in this field but e.g “1”

eg.
If I edit an Report and choose for the field Main Group the value “–None–” after save it will haven an Value and the table field: aor_reports.group_display will have an entry and not be “NULL” anymore.

Repair functions were not made a change and I not found similar on the Forum, has anyone a similar Issue or an tip were I could search for the root cause? many thanks

2

Hey there,

Thanks for raising this

I’ve upgraded a local instance from 7.11.15->7.11.17 and can see the issue as you’ve described

(ie: Selecting “–none–” will default to another value, and won’t save as “–none–”)

It seems like there were some changes to the Reports functionality in 7.11.16, so it is entirely possible that something has changed that causes this
https://docs.suitecrm.com/admin/releases/7.11.x/#_7_11_16


You can see the commits that differ in 7.11.15 and 7.11.16 here, if you would like to search for a root cause:
https://github.com/salesagility/SuiteCRM/compare/v7.11.15…v7.11.16


However, I’d recommend raising this on the Github repo as a bug, as it does indeed look like an issue:
https://github.com/salesagility/SuiteCRM/issues

There, it can be logged and addressed
(Or I can raise it, if you’d like)

Thanks for letting us know!

3

first of all a big thank you, would be great and appreciated if you kindly log a bug to Github

4

Hey,

Just wanted to let you know i’ve raised it as a bug, here:

1 Like
5

FYI, This new problem is also happening in version 7.10.28.

1 Like
6

Hey folks,

There has recently been a Pull request on github that contains a fix for this issue:

I’ve given it a try on 7.11.17, and I appear to be able to save with “–none–” selected now.

Would you be able to make the changes noted here, and let us know if this resolves the issue?

2 Likes
7

The updates appear to be working fine now on 7.10.28. Thank you for the quick fix!

1 Like
8

only FYI: the latest upgrade SuiteCRM 7.11.18 fix this issues…again many thanks to all

2 Likes