By using AWS re:Post, you agree to the Terms of Use
/Amazon QuickSight/

Questions tagged with Amazon QuickSight

Sort by most recent
  • 1
  • 90 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Quicksight: Navigation Action with parameters doesn't update the controls in the new tab

Hello! I have an analysis in Quicksight with two tabs - one is an "overview" tab where we look at all of our units, and then there's a "deep dive" tab where it gives more detail about a single unit. The "overview" tab has a table where it lists all of the units and various metrics for them. I want to be able to click on a row in that table, and have it take me to the "deep dive" tab. When it goes to the deep dive tab, I want it to fill in a couple controls on the new tab (like the unit serial number) so that all the visuals filter by that serial number, and the tab is showing me just information about this specific unit. It seems like a Navigation Action with updating parameters is the way to go, but it doesn't work. When I click on the row I want (both in the analysis and the dashboard), it takes me to the deep dive tab, but it doesn't fill in the controls, so they still display "all". it seems like this is not the functionality intended. In the "Action" tab for the visual in the "overview" tab, I have selected the following options: Activation: "Select" Action Type: Navigation Action Target Sheet: deep dive tab Parameters: Here I have listed the parameters I want to fill, and the fields that correspond to them. Again, when I click on the row, it takes me to the new tab, but it doesn't fill in the parameters. Is this a bug or is this as intended? If it's intended, how do I make it so users can click on a row and it takes me to the deep dive tab and fills in the controls so that the visuals filter by the control values?
1
answers
1
votes
11
views
asked 2 days ago

What is the best way to plot array types in quicksight

Is it possible to plot X-Axes values in SignalX_Sampled_messsignal and Y-Axes values in SignalX_Sampled_zeitvektor) in QS Data example: ``` SignalX_Sampled_messsignal,SignalX_Sampled_zeitvektor [47.5, 47.5, 47.5, 47.5, 47.5, 47.5, 47.5, 47.5, 47.5],[-1016, -816, -616, -416, -216, -16, 184, 384, 584] [26.25, 26.25, 26.25, 26.25, 26.25, 26.25, 26.25, 26.25, 26.25],[-1015, -815, -615, -415, -215, -15, 185, 385, 585] [18.25, 18.25, 18.25, 18.25, 18.25, 18.25, 18.25, 18.25, 18.25],[-1045, -845, -645, -445, -245, -45, 155, 355, 555] [79.75, 79.75, 79.75, 79.75, 79.75, 79.75, 79.75, 79.75, 79.75],[-1045, -845, -645, -445, -245, -45, 155, 355, 555] [7.75, 7.75, 7.75, 7.75, 7.75, 7.75, 7.75, 7.75, 7.75, 7.75],[-1076, -876, -676, -476, -276, -76, 124, 324, 524, 724] [26.75, 26.75, 26.75, 26.75, 26.75, 26.75, 26.75, 26.75, 26.75],[-1006, -806, -606, -406, -206, -6, 194, 394, 594] [13.75, 13.75, 13.75, 13.75, 13.75, 13.75, 13.75, 13.75, 13.75, 13.75],[-1144, -944, -744, -544, -344, -144, 56, 256, 456, 656] [67.75, 67.75, 67.75, 67.75, 67.75, 67.75, 67.75, 67.75, 67.75],[-1046, -846, -646, -446, -246, -46, 154, 354, 554] [43.25, 43.25, 43.25, 43.25, 43.25, 43.25, 43.25, 43.25, 43.25, 43.25],[-1127, -927, -727, -527, -327, -127, 73, 273, 473, 673] [22.5, 22.5, 22.5, 22.5, 22.5, 22.5, 22.5, 22.5, 22.5],[-1046, -846, -646, -446, -246, -46, 154, 354, 554] [25.75, 25.75, 25.75, 25.75, 25.75, 25.75, 25.75, 25.75, 25.75],[-1044, -844, -644, -444, -244, -44, 156, 356, 556] [25.75, 25.75, 25.75, 25.75, 25.75, 25.75, 25.75, 25.75, 25.75, 25.75],[-1066, -866, -666, -466, -266, -66, 134, 334, 534, 734] ```
0
answers
0
votes
14
views
asked 15 days ago
1
answers
0
votes
12
views
asked 2 months ago

Set parameter value programatically while generating QuickSight embedded report URL

I am working on the QuickSight embedded report url generation. I am trying to set the parameter default value programatically using below JAVA code.It is not working. ``` GetDashboardEmbedUrlRequest req = new GetDashboardEmbedUrlRequest() .withAwsAccountId(awsAccountId) .withDashboardId(reportInput.getDashboadId()) .withUserArn(userArn) .withIdentityType(EmbeddingIdentityType.QUICKSIGHT) .withSessionLifetimeInMinutes(sessionTimeout); req.putCustomQueryParameter("CampaignName", "ABC"); req.putCustomQueryParameter("reportDev", "Program"); // get the dashboard URL String embedUrl = quickSightClient.getDashboardEmbedUrl(req).getEmbedUrl(); LOGGER.info("URL:{}",embedUrl); ``` In the above code, "CampaingName" is multivalues parameter attached to the dropdown control. It's default value is set to "[All]" while building a report. Parameter "reportDev" is single value parameter with no default value and no control or any thing attached to it. Dummy parameter I introduced for testing. After running the code, when I copy the url printed in console by logger and run it in the browser, report opens properly but with "CampaignName" and "reportDev" both set as "ALL". Sample generated ulr is as below ``` https://xx-xxxx-x.quicksight.aws.amazon.com/embed/xxxxxxxxxxxxxxxxx/dashboards/xxxxxxxxxxxxxxxxxxx?code=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&identityprovider=quicksight&isauthcode=true ``` Well if I get the dashboard url and pass the parameter in the url to, it worked properly. "CampaignName" is set to "ABC" and "reportDev" set to "Program". According the data in the report also got filtered. Url working corrctly as below. ``` https://xx-xxxx-1.quicksight.aws.amazon.com/embed/xxxxxxxxxxxx/dashboards/xxxxxxxxxxxxxxx#p.reportEnv=Program&p.CampaignName=ABC ``` Can anybody please tell me what is missing in my code. I tried below variation as well but no luck. ``` req.putCustomQueryParameter("p.CampaignName", "ABC"); req.putCustomQueryParameter("p.reportDev", "Program"); ```
1
answers
0
votes
8
views
asked 2 months ago

Error in Visual: The dataset changed too much for QuickSight to automatically update your analysis. You can edit the fields or filters in the current dataset, or replace it with a different dataset.

I created a heat map visual in a QuickSight analysis. It used to work, and now it is giving this error: > The dataset changed too much for QuickSight to automatically update your analysis. You can edit the fields or filters in the current dataset, or replace it with a different dataset. I can't find anything about this error on google or in re:Post, and would appreciate some help in figuring out what causes this. There is a link for further information but it just takes me to the QuickSight front page. Here are other details that may be pertinent: 1. The row contains a single string identifier, the column is a datetime column, and the measure is an integer 2. The error says the dataset changed, and I believe this to be the case, but I'm not 100% certain how it changed (it was modified by someone else and I don't recall how it differs from how it originally was). 3. The dataset currently joins a custom SQL query dataset with a dataset that pulls an entire table from our DB. The two datasets are joined on a string column that's not unique in either dataset. 4. We pull all our data from a Redshift DB 5. When I remove any of the new columns that were added and leave just the barebones ones I need here, I still see the error 6. If I delete the analysis and try to create a new one with this dataset, it will show me the error the moment I add any column into any field well. If I delete the column from the field well, it still shows the error even though there are no longer any values in the empty field wells. it seems like something just... broke the dataset. Any help with this appreciated, thank you for taking the time to read this.
2
answers
0
votes
54
views
asked 2 months ago

DataSourceArn error for Athena Quick sight in cfn template

AWSTemplateFormatVersion: '2010-09-09' Description: 'Creating QuickSight data source' Resources: QuickSightDataSource: Type: AWS::QuickSight::DataSource Properties: AwsAccountId: !Ref AWS::AccountId Name: Testing Data Source Type: ATHENA DataSourceId: testing-data-source DataSourceParameters: AthenaParameters: Workgroup: primary Permissions: - Actions: - quicksight:DescribeDataSource - quicksight:DescribeDataSourcePermissions - quicksight:PassDataSource Principal: !Sub - 'arn:aws:quicksight:us-east-1:${Account}:user/default/my-user-name' - Account: !Ref AWS::AccountId QSDataSet: DependsOn: QuickSightDataSource Type: AWS::QuickSight::DataSet Properties: AwsAccountId: !Ref 'AWS::AccountId' DataSetId: 'QSDataSet-test' ImportMode: SPICE Name: Dataset-test Permissions: - Actions: - 'quicksight:CreateDataSet' - 'quicksight:DeleteDataSet' - 'quicksight:DescribeDataSet' - 'quicksight:DescribeDataSetPermissions' - 'quicksight:PassDataSet' - 'quicksight:UpdateDataSet' - 'quicksight:UpdateDataSetPermissions' Principal: !Sub - 'arn:aws:quicksight:us-east-1:${AWS::AccountId}:user/default/my-user-name' - Account: !Ref 'AWS::AccountId' PhysicalTableMap: downtime_data_json: DataSourceArn: !GetAtt QuickSightDataSource.Arn InputColumns: - Name: downtime Type: INTEGER Schema: XXX??? I have data source & data tables in Athena and want to refer that in above template. I am not finding DatasourceArn, the above template throwing error as Model validation failed (#: extraneous key [DataSourceArn] is not permitted)". can anyone please help me out to hash out this.
0
answers
0
votes
1
views
asked 2 months ago

Embedding a Quicksight QSearchBar for a user in a namespace (other than default)

I am able to successfully embed Quicksight dashboards using the multitenancy (namespaces-based) approach described in Quicksight's documentation. However, when I try to embed a Q Search Bar, the request completes successfully, but it generates a blank iFrame. Are Q Search Bars only allowed to be embedded for users in the default namespace? If not, how can I go about granting access to Q Topics to users in different namespaces and successfully embedding the Q Search Bar? Here are some additional details: I've followed the Amazon Quicksight documentation for embedding dashboards for registered users as well as embedding the Q search bar for registered users. I've created a workflow that creates namespaces and uses row level security to restrict access based on namespaces / groups. While the dashboard embedding works fine for users created in their respective namespaces, the Q Search Bar embedding does not. This applies even if I create a Q Topic from the same dashboard that I can embed successfully for the namespace user. In both cases, the result is simply a blank iframe where the Q Search Bar should appear. The actual call to GenerateEmbedUrlForRegisteredUser does not throw an error when attempting to embed the Q Search Bar for a user from the namespace - the returned link just generates a blank iFrame. However, if I use same operation ( GenerateEmbedUrlForRegisteredUser) using the OWNER account in the default namespace, the embedded Q Search Bar works fine. This appears to suggest that there is some sort of permissions issue at play. I cannot find any documentation that covers how to use the API to grant access to a Q Topic to a user in a specific namespace. I've tried removing RLS as well, but the iFrame is still empty. Any help would be greatly appreciated.
2
answers
0
votes
4
views
asked 3 months ago

How to make a Year-Over-Year Line Chart in QuickSight

Hello, I need help to understand if there is a way to display year-over-year data in a line chart. For my particular example, I am plotting vehicle rentals over time. I want to plot the date the rental occurs on the x-axis and the count of total rentals for that day on the y-axis. The tricky part is that I want to show the data with a year-over-year comparison and that is where I need help. I am aware of the Color field for Line Charts that allows grouping different lines over one another by different dimensions. However, I cannot do this because I am already using the date field along the x-axis...QuickSight tells me "You can't use the same field for more than one dimension (blue) field well. Choose different fields for them" Essentially what I want is for the x-axis to show all the months (or days) from January to December. Then Each different color line will represent the count of rentals for each year. Ideally, this would be drillable too, so a user could drill down to the week or day view but preserve the year-over-year view. Here is an image that I've created demonstrating this: [YoY Line Chart](https://drive.google.com/file/d/1YmNVkl9yKNjrYvtyOqP6ZTs7VAiJhOsA/view?usp=sharing) I have come up with a workaround by creating a calculated field to extract each part of the date (year, month, date, etc) so that QuickSight doesn't scold me for using the same field in multiple dimension field wells. The problem with this is that then those fields are no longer of the DateTime type. I don't like this because I lose the value of using Dates in a Line chart (relative date filtering, automatic drilling, etc.) and, if it isn't a date, QuickSight can only sort alphabetically (April comes before January, etc.) Does anyone have a technique for showing YoY trend data in the way I've described? Thanks
2
answers
0
votes
10
views
asked 4 months ago

Athena QuickSight query timesout

I am using Athena to connect to my DocumentDB database with the intention of visualising the data in QuickSight. I can see the connection is correct as the database name and table name load properly. When I go to create an analysis or even preview the data it timesout. A refresh just causes the same result. The table only contains 40 or so documents so its not an issue of the amount of data. I have tried with direct query and SPICE. This is the error returned when attempting to reconnect from QuickSight: ``` Error Details Error type: SQL_EXCEPTION Learn more Error details: [Simba][AthenaJDBC](100071) An error has been thrown from the AWS Athena client. GENERIC_USER_ERROR: Encountered an exception[com.amazonaws.SdkClientException] from your LambdaFunction[arn:aws:lambda:eu-west-1:717816899369:function:documentdb-connector] executed in context[retrieving meta-data] with message[Unable to execute HTTP request: Connect to s3.eu-west-1.amazonaws.com:443 [s3.eu-west-1.amazonaws.com/52.218.57.91] failed: connect timed out] [Execution ID: 56486351-0cba-4e81-9d9f-3ff4722c198f] Ingestion Id: 061d9b7e-c7f3-49a7-88ba-531551f6cc9a ``` The SQL_EXCEPTION errors states that it can be caused by a timeout so I figure thats the issue. `SQL_EXCEPTION – A general SQL error occurred. This error can be caused by query timeouts, resource constraints, unexpected data definition language (DDL) changes before or during a query, and other database errors. Check your database settings and your query, and try again.` Could there be an issue with the Lambda function being used by Athena to connect to the DocumentDB? Looking at the logs the connection seems to be working. I thought QuickSight would just be able to pull in the data now that everything is linked up. Any advice is appreciated.
0
answers
0
votes
9
views
asked 4 months ago
  • 1
  • 90 / page