Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Database mapped field in model metadata shows None after mapping/saving #42355

Open
maxzheng opened this issue May 7, 2024 · 0 comments
Open

Database mapped field in model metadata shows None after mapping/saving #42355

maxzheng opened this issue May 7, 2024 · 0 comments
Labels
Priority:P3 Cosmetic bugs, minor bugs with a clear workaround .Team/QueryingComponents Type:Bug Product defects

Comments

@maxzheng
Copy link
Contributor

maxzheng commented May 7, 2024

Describe the bug

In a model's metadata, I edited a field to map the database field. It mapped, however it still shows None.
Screenshot 2024-05-03 at 2 52 21 PM

To Reproduce

  1. Edit any model and map a field to a database field
  2. Observe the mapping shows None even though it mapped and works.

Expected behavior

It should show the mapped field

Logs

No response

Information about your Metabase installation

Master on Postgres

Severity

Cosmetic

Additional context

No response
@maxzheng maxzheng added Type:Bug Product defects Priority:P3 Cosmetic bugs, minor bugs with a clear workaround .Team/QueryingComponents labels May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority:P3 Cosmetic bugs, minor bugs with a clear workaround .Team/QueryingComponents Type:Bug Product defects
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@maxzheng