Hi all - Our team identified what appears to be a significant bug with QS - it is not correctly calculating YOY growth when inputted as a calculated field - has anyone else experienced this and know ways around it? We’ve raised a SIM but haven’t heard back yet

Hello @cmot , Do you have some examples where this is not working? Maybe create an Arena dashboard and share with the community so we can all take a look? Thanks!

Hi @andres007 - I don’t believe I’m allowed to share as it contains confidential team data - I can describe the situation however - we created the YoY calculation (below) which works fine as long as no filters are in place - however when a filter is put in for a bd product code, the YoY calculation …

Hi, Can you share how are you calculatin the 2023 and 2024 revenue fields? The unexpected result might be related to the way Quick Sight calculates the agregations. Have you looked at this documentation for Level Aware Calculations? Using level-aware calculations in Amazon QuickSight - …

Thanks @andres007 - The calculation for 2023 and 2024 revenue is: 2024 Rev: ifelse((extract(‘YYYY’,{sales_revenue_month_start_date})=2024),{sales_revenue_dollar_amount},NULL) 2023 YTD Rev: ifelse((extract(‘YYYY’,{sales_revenue_month_start_date})=2023) AND (extract(‘MM’,{sales_revenue_month_star…

Also thank you for recommending the LAC A function, unfortunately it returned the same result

Hello @cmot , my thought is you will want to utilize LAC-W aggregations rather than LAC-A. Also, how are you applying the bp product code filter? Is it based on a parameter, and if so is it single value or multi value? If you alter the 2023 YTD Rev and 2024 Rev calculated field to look like this: 2…

Thanks @WLS-DM , this is a brilliant approach. @cmot , we hope this solution works for you. Let us know if this is resolved. And if it is, please help the community by marking the above answer as a “Solution.” (click the check box under the reply) In case you need further assistance with your problem…

Hello @cmot , since we have not heard back from you, I will mark my last response as the solution. Let me know if you have any remaining questions on this issue. Thank you!

Hi @WLS-DM ! Apologies for delay - I just needed some time to circle back to this issue. It’s not based on a parameter, its just a simple multi-value select filter for the BD Product Code. I tried replacing all my calculations with the Lac-W calculation you mention above, however it instead provide…

Hi @Xclipse - thanks for checking in. Appreciated Dylan’s response but unfortunately it didn’t resolve the issue.

Bug Identified for QS Calculated Field

Q&A

Xclipse May 23, 2024, 2:46am 12

Thanks @cmot, please can you create a sample dashboard with sample dataset showing your problem state using Arena and post it here. (Details on using Arena can be found here - Quick Sight Arena

Topic		Replies	Views
YOY calculation got errased Q&A calculation , calculations-editor , calculated-field , quick-sight , calculations , Business-Intelligence-Engineer	3	128	November 16, 2024
Creating Calculated Fields for multiple custom date filters in one visual Q&A quick-sight , visuals , calculations , Business-Intelligence-Engineer	2	319	January 22, 2024
Illustrate YoY Growth Rates and hide original values Q&A quick-sight , calculations , Business-Intelligence-Engineer	3	100	August 27, 2024
Incorrect Value returned when doing YOY change Q&A analysis , error , quick-sight , calculations , Business-Intelligence-Engineer	3	109	July 12, 2024
YoY formula not working when filtering out last year's data Q&A admin , quick-sight , reports , qls-reporting	1	412	January 16, 2024

Bug Identified for QS Calculated Field

Related topics