# Pre aggregate when connecting dataset

**URL:** <https://community.amazonquick.com/t/pre-aggregate-when-connecting-dataset/50977>\
**Category:** Q&A\
**Tags:** data-source, feature-request, Business-Intelligence-Engineer, quick-sight\
**Created:** [December 22, 2025, 9:30am UTC](https://community.amazonquick.com/t/pre-aggregate-when-connecting-dataset/50977 "2025-12-22T09:30:07Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![wantiqic](https://avatars.discourse-cdn.com/v4/letter/w/ce7236/32.png) [@wantiqic](https://community.amazonquick.com/u/wantiqic)\
**Post date:** [December 22, 2025, 9:30am UTC](https://community.amazonquick.com/t/pre-aggregate-when-connecting-dataset/50977/1 "2025-12-22T09:30:07Z")

</div>

I have two datasets, and the other dataset has too much segmented data. I hope to aggregate certain fields, like “Group by” in SQL, and then use these fields as connection keys to connect the two datasets. Otherwise, when connecting two datasets, the datasets will be copied into many copies. For example, Table 1 has name, account, and revenue. Table 2 has names and gms. When two tables are connected, revenue is added to each account using name as the key. (Because there are other fields present, we cannot simply use the average value). I hope the final table format will be: name, revenue (total account), gms. How can I do that？

---

<div class="post-metadata">

**Author:** ![JacobR](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/jacobr/32/37779_2.png) [@JacobR](https://community.amazonquick.com/u/JacobR)\
**Post date:** [December 22, 2025, 4:04pm UTC](https://community.amazonquick.com/t/pre-aggregate-when-connecting-dataset/50977/2 "2025-12-22T16:04:02Z")

</div>

Hi @wantiqic ,

I think I understand what you are trying to do. Essentially you want to combine both tables by name and show the total revenue by name. I would try this to start:

– For Table 1 (aggregate by name)  
SELECT  
name,  
SUM(revenue) as total\_revenue  
FROM table1  
GROUP BY name

– Then join with Table 2  
SELECT  
t1.name,  
t1.total\_revenue as revenue,  
t2.gms  
FROM (  
SELECT name, SUM(revenue) as total\_revenue  
FROM table1  
GROUP BY name  
) t1  
LEFT JOIN table2 t2 ON t1.name = t2.name

Let me know if this helps!

---

<div class="post-metadata">

**Author:** ![wantiqic](https://avatars.discourse-cdn.com/v4/letter/w/ce7236/32.png) [@wantiqic](https://community.amazonquick.com/u/wantiqic)\
**Post date:** [December 25, 2025, 8:19am UTC](https://community.amazonquick.com/t/pre-aggregate-when-connecting-dataset/50977/4 "2025-12-25T08:19:47Z")

</div>

Thanks! I understand what you mean.But my goal is to visualize the connected data in the ‘analyses’ function of Quick. I think this should be done in the data editing interface of Quick, but there are no aggregation options or code filling places there.

 ![图片](https://d1wl4jav5dp96l.cloudfront.net/original/3X/3/e/3e3bc652ef0bbf20f73910a5bf497d3368378c26.png)

---

<div class="post-metadata">

**Author:** ![JacobR](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/jacobr/32/37779_2.png) [@JacobR](https://community.amazonquick.com/u/JacobR)\
**Post date:** [January 5, 2026, 4:00pm UTC](https://community.amazonquick.com/t/pre-aggregate-when-connecting-dataset/50977/5 "2026-01-05T16:00:09Z")

</div>

Hi @wantiqic ,

If your goal is to visualize the connected data, then I would recommend you use the new data prep experience. With the new data prep experience there are built in features that are not offered in the old data prep experience like aggregation.

 ![image](https://d1wl4jav5dp96l.cloudfront.net/original/3X/0/1/0180417dc0868e56fb8c1170f656f86eaa7895ac.png)

---

<div class="post-metadata">

**Author:** ![priyaik](https://avatars.discourse-cdn.com/v4/letter/p/db5fbb/32.png) [@priyaik](https://community.amazonquick.com/u/priyaik)\
**Post date:** [January 5, 2026, 4:21pm UTC](https://community.amazonquick.com/t/pre-aggregate-when-connecting-dataset/50977/6 "2026-01-05T16:21:19Z")

</div>

Below is the link on how you can switch to new Data Prep experience. [Features not supported in the new data preparation experience - Amazon Quick Suite](https://docs.aws.amazon.com/quicksuite/latest/userguide/unsupported-features.html)

---

<div class="post-metadata">

**Author:** ![Vaidy](https://avatars.discourse-cdn.com/v4/letter/v/c89c15/32.png) [@Vaidy](https://community.amazonquick.com/u/Vaidy)\
**Post date:** [January 7, 2026, 5:50pm UTC](https://community.amazonquick.com/t/pre-aggregate-when-connecting-dataset/50977/7 "2026-01-07T17:50:18Z")

</div>

Hi @wantiqic ,

We hope this solution worked for you. Let us know if this is resolved. And if it is, please help the community by marking this answer as a “Solution" (check box under the reply)

---

<div class="post-metadata">

**Author:** ![wantiqic](https://avatars.discourse-cdn.com/v4/letter/w/ce7236/32.png) [@wantiqic](https://community.amazonquick.com/u/wantiqic)\
**Post date:** [January 8, 2026, 7:53am UTC](https://community.amazonquick.com/t/pre-aggregate-when-connecting-dataset/50977/8 "2026-01-08T07:53:22Z")

</div>

Thank you. I’m testing the new experience. But one reason I don’t use it directly is that when uploading an Excel file with multiple sheets, there’s a glitch causing incorrect uploads. I believe this is a bug: for example, when I select sheet1, it actually imports sheet2 instead

---

<div class="post-metadata">

**Author:** ![wantiqic](https://avatars.discourse-cdn.com/v4/letter/w/ce7236/32.png) [@wantiqic](https://community.amazonquick.com/u/wantiqic)\
**Post date:** [January 8, 2026, 8:32am UTC](https://community.amazonquick.com/t/pre-aggregate-when-connecting-dataset/50977/9 "2026-01-08T08:32:50Z")

</div>

There are too many bugs in the new Data Prep experience. For example, when I convert data types, both percentages and numbers with a thousand separator style are judged as strings, and when converted to numbers, they are all treated as null values.

---

<div class="post-metadata">

**Author:** ![wantiqic](https://avatars.discourse-cdn.com/v4/letter/w/ce7236/32.png) [@wantiqic](https://community.amazonquick.com/u/wantiqic)\
**Post date:** [January 8, 2026, 10:16am UTC](https://community.amazonquick.com/t/pre-aggregate-when-connecting-dataset/50977/10 "2026-01-08T10:16:12Z")

</div>

Thanks! After switching to the new experience, aggregation is now possible and the issue has been resolved 😄 😄

---

<div class="post-metadata">

**Author:** ![JacobR](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/jacobr/32/37779_2.png) [@JacobR](https://community.amazonquick.com/u/JacobR)\
**Post date:** [January 8, 2026, 3:35pm UTC](https://community.amazonquick.com/t/pre-aggregate-when-connecting-dataset/50977/11 "2026-01-08T15:35:53Z")

</div>

Hi @wantiqic ,

Glad to hear the new data prep experience worked for you! The new data experience is still relatively new so there are a few functions that are still being worked on. This is why they still allow users the ability to switch back to the old data prep experience.
