Quick Chat agent reports empty pivot table visual data when visuals depend on dashboard parameters, despite populated embedded dashboard state

Q&A
, , ,
1

Summary

A Quick Chat agent (Generative Q&A) linked to a dashboard cannot read data from certain parameter-driven pivot table visuals, even when the controlling dashboard parameter has a selected value in the embedded dashboard.

The agent reports those visuals as empty and suggests the user select a value in the parameter control. The same visuals show populated data in the embedded dashboard. Other parameter-driven pivot table visuals on the same sheet (using a different dashboard parameter) can be read successfully by the agent.

Environment

  • Quick Chat SDK embed + separate embedded dashboard embed

  • Dashboard parameters passed via contentOptions.parameters from DescribeDashboardDefinition defaults

  • Missing defaults reapplied with embeddedDashboard.setParameters() before prompts

  • No GetDashboardSheetData filter overrides in the client integration

  • Quick Chat embed URL includes experience configuration only; no additional parameters or filters in the chat embed request

Affected resources

Resource Details
Visual type Pivot table
Dependency Visual title and/or calculated fields reference a dashboard parameter via dynamic placeholder (e.g. <<$parameter-id>>)
Parameter control Single-select dashboard parameter bound to the visual
Comparison Other pivot table visuals on the same sheet, also parameter-driven but bound to a different dashboard parameter, return data to Quick Chat

Steps to reproduce

  1. Configure a Quick Chat agent to consume a dashboard containing parameter-driven pivot table visuals.

  2. Embed the dashboard with parameter defaults from DescribeDashboardDefinition.

  3. On the target sheet, confirm the relevant dashboard parameter has a selected value in the embedded dashboard UI.

  4. Send a Quick Chat prompt asking for data from those pivot table visuals.

  5. Result: Quick Chat reports the visuals as empty.

  6. Contrast: The same visuals display populated data in the embedded dashboard.

Expected vs actual

Expected Actual
Visual data in Quick Chat Agent returns pivot table values Agent reports empty visuals
Parameter state Agent respects active dashboard parameter Parameter appears set in embedded dashboard but is not resolved in Quick Chat’s data path
Similar visuals Consistent behavior across parameter-driven pivots on the same sheet One parameter-bound pivot group works; another does not

Hypothesis

Quick Chat’s internal visual data retrieval does not correctly resolve dashboard parameters for certain parameter-driven pivot table visuals, even when:

  • Parameter defaults are passed in the dashboard embed, and

  • setParameters() restores missing defaults before the prompt is sent.

This appears to be a Quick Chat data-consumption issue, not missing dashboard data or client-side filter overrides.

2

Hi @jkubicki,

Thanks for giving so much detail about this issue! A couple of things I would recommend checking. First, is there a difference in how the working vs non-working parameters are defined? For example, are the failing ones using dynamic defaults vs static defaults? Or are they multi-value vs single-value? Second, are the failing visuals using the parameter in a calculated field expression vs just in the visual title? If it’s specifically calculated fields that reference <<$parameter-id>>, that might be the distinguishing factor.

Hope this helps narrow it down a bit and feel free to keep us posted with any new updates or questions you have regarding this.

3

Static Defaults seem to work if you specifically select the dashboard for context or have its knowledge base on the agent. However the only ones I checked were single values, we do not have an multi-values for this dashboard.

The visuals using the parameter work fine and do update correctly when changing on the dashboard.

It does seem to be specifically be that the SDK Quick Chat can not understand the <<$parameter-id>> field.

Lastly, using the Quick Chat within Quick Suite, it can see <<$parameter-id>>, this seems to be only a limitation in the SDK version.

Let me know if you have any more questions to help solve this issue.

4

Hi @jkubicki,

Thanks for confirming. From what you mentioned above, I believe this is a bug since the console version resolves the parameter context correctly, but the embedded SDK version doesn’t pass or resolve that parameter state when reading visual data. I’d recommend opening a support ticket (Case management - AWS Support). When you open it, I would include that this is SDK-embed specific (works in console), the distinction between working parameters and failing ones (static vs <<$parameter-id>> dynamic placeholders), and that that setParameters() is being called before prompts.

Hope this gets resolved quickly and keep us posted!

5

Hi @jkubicki,

Just checking back in since this thread hasn’t received a response in a while. Was Cesar’s reply helpful to you and/or were you able to find a solution yourself in the meantime? Please help the community by marking this answer as “Solution” or following up in general within the next 3 business days!

Thanks!

6

Hi @jkubicki,

Since we haven’t received any further updates from you, I’ll treat this inquiry as complete at this time. Please feel free to create a new post if you have more questions.

Thank you.