we just upgraded from 8.7 to 8.8 reports were working fine now whenever we add a custom field report doesn’t load any data and i checked log and found out that the query fails as it isn’t getting the custom field from the cstm table in database
Wed Aug 13 2025 at 07:53:26 [3232271][seed_max_id][FATAL] Mysqli_query failed.
Wed Aug 13 2025 at 07:53:26 [3232271][seed_max_id][INFO] Query Execution Time:0.0009620189666748
Wed Aug 13 2025 at 07:53:26 [3232271][seed_max_id][FATAL] Query Failed: SELECT count(*) c FROM (SELECT `opportunities`.name AS 'Opportunity_Name0', `opportunities`.assigned_user_id AS 'Assigned_to1', `accounts`.id AS 'Customer2', `opportunities`.opportunityid_c AS 'Opportunity_Id3', `opportunities`.id AS 'opportunities_id', `accounts`.id AS 'accounts_id' FROM `opportunities` LEFT JOIN accounts_opportunities `opportunities|accounts` ON `opportunities`.id=`opportunities|accounts`.opportunity_id AND `opportunities|accounts`.deleted=0
Your first field in the report is a standard field?
How does your screen look like, when you execute the report?
And your using aggregates as well as it seems?
If it’s not the linked issue, can you find it in the Github tickets?
MySQL error 1054: Unknown column 'opportunities.custom_opp_id_c' in 'field list'
and that is correct - it would need to look inside the cstm table for that field.
I haven’t found this exact issue in the Suite8 queue. Maybe is the issue exists in Suite7 as well.
Do you want to create a ticket?
Otherwise I’d do it later on.
Yes, I’ve added some - still doesn’t show.
It seems like the report is simply checking the wrong table - at least if the logged query is the one that’s actually being used for the report.
Actually @hserour
I’ve tested around a bit further.
Can you move your custom field to the 2nd position of the report?