Description
A scheduled report with Omit if no records set to True, generates the following error:
Table name cannot be null: java.lang.IllegalStateException: Table name cannot be null: com.glide.db.TableDescriptor.<init>
Steps to Reproduce
- Log in to the instance as admin.
- Navigate to Reports > View / Run.
- Create a new report with title Incident Test.
4. Set the following options:- Table: Incident
- Condition: Active is true
- Save the report.
- Click the Save button dropdown menu and select Schedule.
- Set the following options.
- Users: System Administrator
- Omit if no records: Checked/True
- Time: (Set to 1-2 minutes from current time)
- Save the report.
- Wait for it to run.
If Omit if no records is true, then the following error is generated in the system logs:
Table name cannot be null: java.lang.IllegalStateException: Table name cannot be null: com.glide.db.TableDescriptor.<init>(TableDescriptor.java:77)
com.glide.db.TableDescriptor.get(TableDescriptor.java:82)
com.glide.db.CompositeElement.<init>(CompositeElement.java:86)
com.glide.db.conditions.SpecialCases.get(SpecialCases.java:70)
com.glide.db.QueryString.buildCondition(QueryString.java:627)
com.glide.db.QueryString.processCurrentTerm(QueryString.java:544)
com.glide.db.QueryString.buildConditions(QueryString.java:481)
com.glide.db.QueryString.deserialize(QueryString.java:273)
com.snc.automation.MailReportJob.combineQueries(MailReportJob.java:179)
com.snc.automation.MailReportJob.reportHasRecords(MailReportJob.java:167)
com.snc.automation.MailReportJob.shouldExecute(MailReportJob.java:149)
com.snc.automation.MailReportJob.valid(MailReportJob.java:66)
com.snc.automation.MailReportJob.execute(MailReportJob.java:46)
com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:103)
com.glide.schedule.JobExecutor.execute(JobExecutor.java:89)
com.glide.schedule.GlideScheduleWorker.executeJob(GlideScheduleWorker.java:219)
com.glide.schedule.GlideScheduleWorker.process(GlideScheduleWorker.java:157)
com.glide.schedule.GlideScheduleWorker.run(GlideScheduleWorker.java:67)
Workaround
The issue is fixed in Jakarta. As a workaround on earlier releases, uncheck the Omit if no records field.
Related Problem: PRB1160081