Dataset Parameter is not working in Paginated report

Question & Answer
, ,
1

Hi, The dataset Parameter i have set in my dataset which is working great with the interactive sheet. But it comes to paginated report. It’s not working.
I’m using the same dataset for both the paginated and Interactive. When i embedded the dashboard i was able to see the filtered out data in interactive sheet but in paginated it was not able to filter out the dataset. It is just showing the default value dataset.
This is a production issue. could you rectify as soon as possible

2

In the earlier release it was working great. I have done a production release for that feature as well. But now with the new release. I don’t think it was tested well. Please plan to resolve this as soon as possible

3

Hi,

check this one may help you

Regards,
Naveed Ali

4

Hi @Naveed,

It 's not about i don’t know how to use the paginated feature. But i’m reporting a bug.

The filter is working great for my analysis. Once i download the published dashboard pdf. The data inside is showing the default value that’s not the expected behaviour right.

1 Like
5

Summary of the issue:

The bug involves a dataset parameter that works correctly in an interactive sheet but fails in a paginated report on AWS. I have a setup with 10 datasets, each containing a parameter with the same name across all datasets. I’ve added this dataset parameter to the URL to filter analyses based on the parameter passed in the URL.

In the interactive sheet, this setup works flawlessly. However, when I download the paginated report as a PDF, the data shown is for the default value set in the dataset parameter, not the filtered data based on the URL parameter.

To replicate the issue:

  1. Use a setup with multiple datasets, each having a parameter with the same name.
  2. Add the dataset parameter to the URL to filter analyses.
  3. Generate an interactive sheet and a paginated report using the same dataset and parameterized URL.
  4. Download the paginated report as a PDF from the published dashboard and observe that it shows the default dataset value instead of the filtered data.

This bug is critical as it affects production reports and analyses. Could you please prioritize this issue and provide an estimated timeline for resolution?

6

@DylanM @Naveed Can you please provide an update?
As we integrated quicksight with our product this will give our product a bad review. Response from your end is expected

7

Hi @uday,

Thank you for letting us know. I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!

8

@andres007
I have informed our team regarding the same. They also have the basic plan which we were not able to raise a support case. Could you please raise a case from your side as this is an bug which needs to be solved, which was not their in the earlier versions. Hope you understand the urgency and compliance issue with this bug. Please prioritize this.

9

@andres007 any update on the bug?

10

Hi @uday, found this post from the products team - Controls is not supported with Paginated Reports at this point but a Feature Request that we are tracking.

As this is a fairly new offering, more features are being added on a regular basis, so please keep an eye on the What’s New / Blog . You can set up a Watching Alert by clicking on the bell icon.