Skip to main content
Question

Quicksight Report Refresh Parameters

  • May 26, 2026
  • 3 replies
  • 31 views
T
Superhero (Partner)
Forum|alt.badge.img+14

I can create a Query using Query Designer with a parameter.  I can then create a Quicksight report based on the published Query.  I can go to Order Report and am prompted for a value for my parameter.  All is well with the world.  If I want to add another parameter to my Query in Query Designer, I can do that and Synchronize the Query.  If I then go to Order Report and refresh the screen, my new parameter appears.  If I give the new parameter a value, I get an error.

P1Rep/QsrParameters (server error)
Malformed Request.
Error details: [{"code":"UNKNOWN_CONTENT","message":"'ParamAbcClass' can not be mapped as a property or an annotation."}]

Server stack trace error(s):
  Tree should be empty but still has content left: ParamAbcClass

I’ve tried Unpublish/Republish too.  I’ve also tried unpublishing my Quicksight report and republishing.  

The only thing that works, is to recreate the Quicksight report based on the updated Query.  Surely this can’t be the solution?  

3 replies

ashen_malaka_ranasinghe
Hero (Employee)
Forum|alt.badge.img+14

Hi ​@Tracy Norwillo,

Following is not a simple refresh/sync issue, it’s a metadata contract mismatch between the Query and the QuickSight report definition (QSR).

'ParamAbcClass' can not be mapped as a property or an annotation
Tree should be empty but still has content left: ParamAbcClass

After adding a new parameter in Query Designer and clicking Synchronize, the system updates the UI (parameter appears). But seems like the underlying QSR parameter schema is NOT fully regenerated.

So, at runtime:

  • Report sends parameter payload including ParamAbcClass
  • Report service cannot map it → UNKNOWN_CONTENT + malformed request

When you rebuild the QuickSight report:

  • A new QSR is generated from the updated query
  • Parameter metadata is clean and aligned

That’s why it becomes the only reliable workaround at the moment. Recreating the QuickSight report is currently the only reliable solution after adding new query parameters as per these observations.

Find me on LinkedIn as Ashen Malaka: https://www.linkedin.com/in/ashen-malaka-ranasinghe/
T
Superhero (Partner)
Forum|alt.badge.img+14
  • Tracy Norwillo
  • Author
  • Superhero (Partner)
  • June 3, 2026

​@ashen_malaka_ranasinghe  Right, I was afraid of that, so in order for Quicksight reports to be a viable tool, we need a way to fully regenerate the schema based on the existing Query.  The current functionality only updates the columns but not the parameters.   It should function like Report Studio does when used for Operational Reports - if I update the model and regenerate, the schema is updated and the json Data Source reflects the change.  Either that or enable the parameter functionality in Report Studio so the parameters can be changed there instead of the Query.  The parameter functionality only works when previewing the report.  When ordering the report, the Report Studio parameters are not exposed.

As a partner, it’s hard to tell our clients that they have to rebuild the report from scratch, if in the future they want to add parameters.  At the very least, this needs to be noted in the documentation as a limitation.

    T
    Superhero (Partner)
    Forum|alt.badge.img+14
    • Tracy Norwillo
    • Author
    • Superhero (Partner)
    • June 4, 2026

    ​@ashen_malaka_ranasinghe  Will you please test this fix in your environment and verify that it works for you too?

    Add a parameter to the Query AFTER the Quicksight report is created, go to the Report Definition for the Quicksight report and click on the Refresh Client Metadata button.  Then order the Quicksight report and refresh the screen showing the parameters.  The new parameter should be there and it should function without errors.

    Terms & ConditionsAccessibility statement