Skip to main content

Troubleshooting

Real symptoms reproduced while building the dashboards, reports, and widgets documented across this section, along with their actual cause and resolution. Ordered by the same sequence as the documentation, grouped by related topic.

Creating a Report​

SymptomLikely CauseResolution
No confirmation appears after saving a newly created report.Unlike a dashboard, no success toast fires when a report is saved for the first time.Trust the navigation to /reports/{id}/builder as the confirmation. The report has saved correctly.

Built-in Reports​

SymptomLikely CauseResolution
A built-in report shows no data at all when first opened.Several seeded reports sit behind a mandatory Filters card that must be filled in, then confirmed with Generate Report, before anything renders.Fill in the required filter and click Generate Report. This is expected behavior for that report, not a loading failure.

Exporting & Sharing Reports​

SymptomLikely CauseResolution
A downloaded PDF contains more or fewer rows than expected.Table Row Count, Current, 100, 500, 1,000, or Custom, controls exported rows independently of whatever is paginated on screen at export time.Check and adjust Table Row Count in the Download PDF Report dialog before exporting.

Widget Types​

SymptomLikely CauseResolution
A widget shows a red Configuration Error panel reading "There is an issue with the fields configuration," with details such as CU is not defined.A calculated field draft was being edited, even one that failed its own Save validation, and the widget's cached query picked up the broken, half-typed expression before it was cleared.Click Refresh on the error panel. This re-runs the widget's query cleanly and clears the error with no other change needed.

Data Fields & Schema​

SymptomLikely CauseResolution
A dimension's values show as raw numbers, such as 381, instead of readable names.That field stores a foreign key but carries only a plain D dimension badge, with no Association back to the table it actually points at.Open Schema and confirm the field carries an A Association badge before using it. If it does not, use a different, genuinely readable dimension, such as Case Reason, or build a calculated field instead.
Dragging a field from a second module does nothing, or that module appears struck through and unselectable.A widget can only query one module at a time by default. Every other module greys out once the widget already has a field from one of them.Use the link icon to open a Blended Data Source and add the second module as its own sub query, instead of dragging it directly into the same widget.

Joins & Calculated Fields​

SymptomLikely CauseResolution
A Schema diagram column name, such as Case_Status, does not match anything when typed directly into the Code tab.The Schema diagram's labels are display names, not the real field reference. The platform actually works with a camelCase, module-prefixed cube name, for example crmServiceCases.caseStatus.Do not type the Schema label directly. Trigger the Code tab's autocomplete with [ and accept the suggested reference instead.
Typing a field name, or a literal ${, in the calculated field's Formula Code box never shows suggestions.The suggestion dropdown only triggers on a literal [ character followed by a module name, not on ${ or a bare field name.Type [, then keep typing the module name, for example [servicecases, and accept one of the real suggestions it returns.
Calculated field Save fails with invalid input value for enum "Status": "...".The expression is syntactically valid, but assigns a value the underlying Postgres enum type does not accept. Save actually compiles and executes the expression against the live schema.Narrow it down through a more specific Ask Auri prompt, or inspect existing data by putting that field on a Table widget first.
Ask Auri generates a correct expression, but Save then fails on an unrelated field.Ask Auri can overwrite the Name field with your raw prompt text, which then fails that field's own "no spaces" validation, while leaving the Expression itself correct.After using Ask Auri, check the Name field before clicking Save, not just the Expression.
Typed text in a Monaco-based editor, either the Formula Code box or the Automations Script node, comes out garbled, reordered, or wrapped in a stray leftover bracket.Fast, simulated keystroke-by-keystroke typing can race with the editor's own input handling and its autocomplete popup.Type more slowly, or paste the text in one action. Always re-read the editor's rendered content, and the validity banner beneath it, before saving.

Filters​

SymptomLikely CauseResolution
A filter is ticked Show in Global Filter, a chip for it appears on the consumer view, but one specific widget on the same page still shows unfiltered data.A global filter only drives a widget that has the identical field dragged into that widget's own Filters zone, with Show in Global Filter ticked on that same row.Open the widget that is not responding, drag the same field onto its own Filters zone, and tick Show in Global Filter there as well.
Ticking Show in Global Filter on a widget's filter changes what that widget shows, even before a global value is chosen.Ticking the checkbox immediately clears and locks the widget's own local value, reverting it to its unfiltered state, until a value is set centrally in the FILTERS tab.Go to the FILTERS tab right after ticking the checkbox and set the value there, optionally ticking Set Default so every viewer sees it applied from the first load.

Sharing, Duplicating & Publishing Dashboards​

SymptomLikely CauseResolution
Cannot find a way to let someone outside the organization, or "anyone with the link," view a dashboard or report.General access in the Share dialog is fixed to restricted in this build. It is disabled, not simply defaulted.Add each intended viewer explicitly as a User, Group, or Role grantee in the Share dialog.
A dashboard or report is Published, but one specific person still cannot open it.Published only controls whether the item is visible to end users in general. It does not add any specific person to the Share list.Check the Share dialog's People with access list separately. Published and Shared are independent gates.

Permissions​

SymptomLikely CauseResolution
A user with Share access to a dashboard cannot edit anything in it.Their role's Reports Configuration, Configure Reports permission is set to No. Share access alone only grants viewing, not building.Enable Configure Reports on their role in Configuration, User Management, Roles, or accept that they are intended as a view-only recipient.