Table "not defined" but it exists and is functional

  • Goal: I would like to get rid of this error as the table is functional and I can't see what part of it doesn't exist.

  • Steps:

  • Details: I've renamed the table and error updates to the new table name... but still functions.

  • Screenshots:

  • App json export: (won't let me as I'm a new user)

Just a stab in the dark here. A script or query references requestTable incorrectly.

Check any JavaScript or Transformer scripts running in Retool. Look for references to requestTable.enabled, requestTable.data, or requestTable.selectedRow and ensure they are correctly linked to the current table name.

Look under the Event handlers section of your table component and ensure no outdated references exist.

1 Like

Hey @Max_Ludden

I have a similar Linting error for a component that certainly exists:

The thing about my setup which I find odd is that the error is generated from the records property of my query, which hasn't yet run in the current app state but does have a value (""). My query is also waiting for a submit button to trigger a bit of code which then triggers the offending Linter query. The only place this query is used is within in this triggering code and nowhere in that code is the component referenced. Strange, for sure.

Another little wrinkle here with the existence of certain components might be related to whether or not the app you are using is a Multi-Page app.

Our team is diligently working on fixing "not defined" linting errors, specifically in cases where the value is actually defined and the app functions as expected despite the error

It's quite complex to fix these bugs. We've made a lot of progress on these errors, but they still come up in certain places :disappointed:

1 Like

Hi, same problem, i also have problem with creating new TAB with SQL with errorname Can not create table 'Players', because it already exists in the database 'alasql'