Page 1 of 1
Javascript error when running any report
Posted: Mon Jun 16, 2025 11:06 pm
by Lala
Hi
I am getting a javascript error when I try to run any of my reports or try to save any sql statement, such as a browse sql
When I check the console I get this:
Screenshot 2025-06-17 090012.png
Does anyone have a solution?
2025-06-17_113250_6850a9a260d9e_nuBuilder_backup.sql.gz
Re: Javascript error when running any report
Posted: Mon Jun 16, 2025 11:55 pm
by steven
Hi Lala,
Can you share a copy of your database?
Steven
Re: Javascript error when running any report
Posted: Tue Jun 17, 2025 12:11 am
by kev1n
Lala wrote: ↑Mon Jun 16, 2025 11:06 pm
Try saving any SQL statement, such as a browse SQL.
Is this related to the topic of your post, "JavaScript error when running any report," or is it a separate issue?
Could you please provide the specific error message you're encountering in this case?
Re: Javascript error when running any report
Posted: Tue Jun 17, 2025 12:17 am
by kev1n
Lala wrote: ↑Mon Jun 16, 2025 11:06 pm
I am getting a javascript error when I try to run any of my reports
Inspect the JS code/the button that runs the report to see if there is any issue. (check the JS code in onclick event)
run_report.png
How to Inspect an Element Using Chrome DevTools (without context menu)
1.
Open Developer Tools
- Press
F12
- Or press
Ctrl + Shift + I (Windows/Linux)
- Or press
Cmd + Option + I (Mac)
2.
Activate the “Select Element” Tool
- Click the pointer icon (top-left of DevTools)
- Or press
Ctrl + Shift + C (Windows/Linux)
- Or press
Cmd + Shift + C (Mac)
3.
Hover and Click an Element
- Move your mouse over the webpage
- Click the element you want to inspect
4.
View in the Elements Panel
- The clicked element will be highlighted in the
Elements tab of DevTools
Shortcut Summary:
Code: Select all
Open DevTools: F12 or Ctrl+Shift+I (Cmd+Option+I on Mac)
Select Element: Ctrl+Shift+C (Cmd+Shift+C on Mac)
Re: Javascript error when running any report
Posted: Tue Jun 17, 2025 1:36 am
by Lala
Ignore this thread please - I've moved the problem to the general thread as it isn't report specific