graphql-engine
graphql-engine copied to clipboard
Console: New relationship UI cannot load relationships on views
Version Information
Server Version: v2.12.0 CLI Version (for CLI related issue): v2.7.0
Environment
- Docker (MacOS)
- Cloud
What is the current behaviour?
When trying to load the relationships on a View, we are faced with this error message:
What is the expected behaviour?
Relationships should be loaded correctly.
How to reproduce the issue?
- Turn-on the New relationship UI feature flag
- Navigate on a View page
- Click the Relationships tab
- Wait until you see the error message
Screenshots or Screencast
Any possible solutions?
Can you identify the location in the source code where the problem exists?
If the bug is confirmed, would you be willing to submit a PR?
Keywords
- relationships
- relationships views
- relationships error
Hello @foxted
Thanks for reporting the issue. I was able to replicate what you are facing in Hasura Cloud v2.12.0-cloud.1
. I can replicate this issue for materialized views as well as non-materialized views too
Short Synopsis
This issue is specifically focused on VIEWS(rather than tables). It works well in old(default) relationship UI (when you toggle off new relationship UI) and you can check that in views -> relationships. In tables, relationships are shown as expected in both new and old(default) UI.
For a specific view(i.e. SQL view), in the new relationship UI, when I looked at network requests for metadata
, it was already containing the necessary/required data for relationship. From that, we can derive that there's no clear issue from the server side. This must be a console issue(though I might be wrong).

I got the same issue with Hasura
Current server version: v2.16.0
Console asset version: a526fad3ff112
Old UI works as intended.
@foxted @meetzaveri This has been fixed in https://github.com/hasura/graphql-engine/commit/498d8fc9f4ad1e9cda8174d3b8afd7629f604713. Feel free to open this thread again if the issue persists.