1
Dashboard visibility requires a separate, undocumented 'createDashboard' mutation not obvious from the page layout creation flow
Source: twentyhq/twenty#25895 · opened by @fcporto-nature
Summary Problem Building a dashboard by creating 'pageLayout'/'pageLayoutTab'/'pageLayoutWidget' records (directly or by copying an existing example) produces no visible or listed dashboard in the UI, with no error raised anywhere. The missing piece is a separate 'dashboard' object record (a distinct entity with just a title and a pageLayoutId) that must be created via its own 'createDashboard' mutation — this is not mentioned in the page layout documentation and is easy to miss entirely. Proposed solution Document the relationship between page layouts and the 'dashboard' object clearly in the dashboards/page-layouts documentation, and/or surface a warning in the UI or API when a page layout of dashboard type exists without a corresponding dashboard record. Additional context Several hours were spent troubleshooting a dashboard that had correct underlying data but never appeared anywhere, before finding the missing 'd…
No pledges yet. Be the first to back this.
Comments
Similar requests
Per-email threads visibility toggle (shared / private)
6 votes · 0 comments
Workflow step mutations are unreachable via workspace API keys (`Forbidden resource`); also hidden from GraphQL introspection
0 votes · 0 comments
Question: Does conditional field visibility exist? (show/hide fields based on Select field value)
3 votes · 0 comments
Feature request: interpolate record-context variables in IFRAME page-layout widget URLs (e.g. {{record.id}}, {{record.fieldName}})
1 vote · 0 comments
System-managed fields cannot be renamed — createdAt/createdBy/updatedAt/updatedBy stay in English on every record page
1 vote · 0 comments
No comments yet.