-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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.
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
If a user has data model access only to one table and this table has FKs, the target is key is empty #21762
Labels
Administration/Permissions
Collection or Data permissions
Administration/Table Metadata
.Frontend
Priority:P3
Cosmetic bugs, minor bugs with a clear workaround
.Reproduced
Issues reproduced in test (usually Cypress)
Milestone
Comments
luizarakaki
added
Priority:P3
Cosmetic bugs, minor bugs with a clear workaround
Administration/Permissions
Collection or Data permissions
Administration/Table Metadata
.Frontend
labels
Apr 19, 2022
Why do we show Orders -> ID as a "foreign" key and allow user to select it for "Orders" table? @luizarakaki |
This was referenced May 1, 2023
8 tasks
Closed
This was referenced Dec 13, 2023
This was referenced Jan 11, 2024
This was referenced May 8, 2024
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Administration/Permissions
Collection or Data permissions
Administration/Table Metadata
.Frontend
Priority:P3
Cosmetic bugs, minor bugs with a clear workaround
.Reproduced
Issues reproduced in test (usually Cypress)
The user shouldn't see the field name, but the current state looks like the FK is not assigned.
Ideally, we should communicate that the field is assigned to a foreign key, but the user doesn't have access to that field.
Field access denied
is a good text short and explicitThe text was updated successfully, but these errors were encountered: