metabase / metabase/metabase

Variable settings tab is disabled/unclickable in native SQL editor when query contains {{variable}}

Open
#73,229 1 comment 0 reactions 0 assignees View on GitHub
.Frontend .Team/Graphy Priority:P2 Querying/Parameters & Variables Type:Bug
Dominant language
Clojure
Stars
49.3k
Forks
6.8k
Avg merge
1d 13h
Merged PRs (30d)
653

Description

### Describe the bug

## Describe the bug

In the native SQL editor, when a `{{variable}}` is added to a query, the "Settings" tab in the Variables side panel is greyed out and cannot be clicked. This makes it impossible to configure the variable type (e.g., Text, Field Filter).

## Version
v0.60.2.5 (Self Hosted)

## To Reproduce

1. Open the native SQL editor
2. Write any SQL query containing `{{variable_name}}` in the WHERE clause
3. Click the `{x}` (Variables) button on the toolbar
4. The Variables side panel opens, but the "Settings" tab is greyed out and unclickable
5. Only the "Help" tab is accessible

## Expected behavior

The "Settings" tab should be clickable, allowing users to configure the variable type (Text, Number, Date, Field Filter) and other settings.

## Actual behavior

The "Settings" tab is disabled regardless of whether the query has errors or runs successfully.

## Additional context

- Tested with both simple queries and complex CTEs
- The issue persists even when the query runs without errors
- Database: PostgreSQL

### To Reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

### Expected behavior

_No response_

### Logs

_No response_

### Information about your Metabase installation

```JSON
{
"browser-info": {
"language": "ja",
"platform": "Win32",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36",
"vendor": "Google Inc."
},
"metabase-info": {
"databases": [
"postgres",
"h2"
],
"run-mode": "prod",
"plan-alias": "",
"version": {
"date": "2026-04-24",
"tag": "v0.60.2.5",
"hash": "d9c91f2"
},
"settings": {
"report-timezone": null
},
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "17.6 (Debian 17.6-2.pgdg12+1)"
},
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.7.8"
}
}
},
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "21.0.10+7-LTS",
"java.vendor": "Eclipse Adoptium",
"java.vendor.url": "https://adoptium.net/",
"java.version": "21.0.10",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "21.0.10+7-LTS",
"os.name": "Linux",
"os.version": "4.4.302+",
"user.language": "en",
"user.timezone": "GMT"
}
}
```

### Severity

This is blocking my usage. I cannot configure SQL variables at all, which prevents me from using dashboard filters with native SQL questions.

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in the native SQL editor with a PostgreSQL query containing a {{variable_name}} in the WHERE clause, then inspect the Variables side panel behavior. Done means the Settings tab is clickable and allows configuration of the variable type, while the Help tab remains available.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql
Domain
databases, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.