Mismatched Aggregation through comparing

[rebecca000827]

i try to compare the current one with the previous one, but there’s always a mismacthed aggregation error

[Giridhar.Prabhu]

Hi @rebecca000827

It appears PreviousBroker is a calculated field from the screenshot and may be what causes this error to appear.

Please review this article from @David_Wong which talks about Level Aware calulations and hopefully you may find the reason for your issue and an answer to how it could be resolved.

Level-Aware Calculations: Tips and Best Practices

[Level-Aware Calculations in Amazon QuickSight] Level-Aware Calculations (LAC) are powerful functions that allow us to perform calculations at a granularity level which is different from the granularity of our datasets and/or visuals. The sample dataset referenced by this article is a dataset of product orders placed by customers. Each order can contain multiple products and each product in an order has a unique Line Item ID. Each row of our dataset represents one line item but we want to per…

If you continue to face issues please provide a bit more detailed information about your dataset, calculated fields in order for us to review and comment.

[rebecca000827]

Hi, Thanks for replying.
The previousbroker is derived from the lag() function to find out the previous broker for that building. What I tried to do here is to find out at which year which building had switched there broker, but it does not allow me to compare the current one with the previous one due to mismatched aggregation

[Brett]

Hi @rebecca000827,
It’s been awhile since last communication took place on this thread; are you still encountering issues or were you able to find a work around for your case?

If still looking for further assistance, could you share the full calculated fields for ‘PreviousBroker’ and ‘InsuranceBroker’?

[Brett]

Hi @rebecca000827,
Checking back in here to see if you had any additional questions regarding your topic?

If we do not hear back within the next 3 business days, I’ll close out this topic.

Thank you!

[Brett]

Hi @rebecca000827,
Since we have not heard back, I’ll go ahead and close out this topic. However, if you have any additional questions, feel free to create a new post in the community and link this discussion for relevant information if needed.

Thank you!