- 新しい順
- 投票が多い順
- コメントが多い順
Hello,
I would like to inform you that Quicksight support multiple visual types and various aggregation modes for data to be visualized in Tables. However, with your explanation, I believe you are trying to retrieve the cumulative data for each month from datasource using a SQL and then visualizing in Analysis as a plain table with "as_of_date" filter. Please correct me if my understanding varies from your setup.
In the sample data you had provided, I see that there is no "as_of_date" column, hence I assume you are referring the "as_of_date" filter to the "date" dataset. In the above data, I see the fields having values as below,
date qty_shipped qty_received qty_adjusted
8/1/23 0 1 0
7/1/23 5 0 0
6/1/23 0 0 7
And, the calculation for "on_hand" field is as below,
SUM(qty_received - qty_shipped + qty_adjusted)
With above data, in case you have "as_of_date" filter having definition as below, it should give the results as you expected.
Condition : Before
Use parameters : true
End date parameter : <<date picker parameter attached to a control>>
Thus, I request you to please verify the Filter definition if it matches above description. Further, in case you continue to observe the issue even after having filter definition as above, I recommend you to kindly consider raising a case to AWS Support team so that an engineer from Quicksight support team can investigate by understanding your setup, usecase and provide you possible mitigation measures.
Thank you !!
関連するコンテンツ
- AWS公式更新しました 2年前
Hi Mounika,
Thank you for the response! The as_of_date filter is just a filter on the "date" field from the dataset that filters out records that have a "date" value after the filter value. So the summed "qty_*" fields should only be from rows that have a "date" before the as_of_date filter value and the "latest_price" column should be populated by the value for "price" from the row with a "date" value closest to or equal to the as_of_date filter value i.e. the most recent price as of the given date filter value.
Thanks again!