Reports on custom module empty after upgrade from 8.7 to 8.8 - Bug in report in version 8.8 (fixed by different order of fields)

We’ve upgraded from 8.7 to 8.8 and now several Reports on a custom modules do now work any more: they return zero lines.

If we re-create those reports (pretty simple) we indeed can select the custom module in the combo box, but do not see any more any field in the Fields …

That’s interesting!

What combo box are you taking about? Which field are missing?

1 Like

but do not see any more any field in the Fields …

Our link https://mysuitecrm/#/bwres_projects

correctly return a list of items

Now I want all those items in a Report, so I click on “+” Report

I see this

with no fields in the Fields (is it ok?)

Fields becomes populated if I clic on “Resales Projects”

Now I add some fields, but when I save the Report return no elements

Yes, that’s how it works. You need to select a module under the Module Tree, then it will display fields in the Fields section.

You should get report with records if you have set the Fields, Conditions or Charts correctly.

Learn more from the doc:

1 Like

yes, exactly, as it happens correctly with other non custom modules.

What can we do to debug?

Make sure you have records into the custom module and you’re using correct fields to display the report.

Can you please share the screenshot of your report? What fields are you using?

1 Like

(sorry I cannot add our data, you sure understand why :wink: )

while report has these

I save, but see no records in report

That’s weird! Just select Project Name in the Fields and then save report.


Check if you have any error in the log files

/logs/Prod/

AND

/logs/legacy/

Also, browser console (shortcut F12)

1 Like

uh, bravo!

with only this field

I see correctly all 93 items in Report

Same with these fields

It works also with

even with this it works

legacy/log_crm.log

but… it does not work if I move “Accounts” to the first position

We do have some FATAL in legacy/log_crm.log

Mon Feb 17 2025 at 18:28:52 [184516][3d34fae9-afbb-2322-3036-5ed106ce103e][FATAL] Mysqli_query failed.
Mon Feb 17 2025 at 18:28:52 [184516][3d34fae9-afbb-2322-3036-5ed106ce103e][FATAL]  Query Failed: SELECT count(*) c FROM (SELECT `bwres_projects`.bwres_projects_accounts_name AS 'Accounts0', `bwres_projects`.name AS 'Project_Identifier1', `bwres_projects`.prj_status AS 'Project_Status2', `bwres_projects`.prj_data_name AS 'Project_Name3', `bwres_projects`.id AS 'bwres_projects_id' FROM `bwres_projects`  WHERE bwres_projects.deleted = 0 ) as n: MySQL error 1054: Unknown column 'bwres_projects.bwres_projects_accounts_name' in 'field list'
Mon Feb 17 2025 at 18:28:52 [184516][3d34fae9-afbb-2322-3036-5ed106ce103e][FATAL] Mysqli_query failed.
Mon Feb 17 2025 at 18:28:52 [184516][3d34fae9-afbb-2322-3036-5ed106ce103e][FATAL]  Query Failed: SELECT `bwres_projects`.bwres_projects_accounts_name AS 'Accounts0', `bwres_projects`.name AS 'Project_Identifier1', `bwres_projects`.prj_status AS 'Project_Status2', `bwres_projects`.prj_data_name AS 'Project_Name3', `bwres_projects`.id AS 'bwres_projects_id' FROM `bwres_projects`  WHERE bwres_projects.deleted = 0  LIMIT 0,100: MySQL error 1054: Unknown column 'bwres_projects.bwres_projects_accounts_name' in 'field list'

(no issue with Firefox inspector)

thank you sooooo much @rsp !!!

Happy that you’re able to see report with data now. Mark answer as solution :white_check_mark: which solved your problem.

I do not know, why it is not working when you put account name as first in the report.

We had the same issue with another report: we solved by setting the first column as a text field (not a link), but we also had to move another column to the third position, or else in the first or second was not working.

This is clearly a bug in version 8.8, while in 8.7 it was working perfectly

related bug