# Calculated field size limit issue

**URL:** <https://community.amazonquick.com/t/calculated-field-size-limit-issue/25723>\
**Category:** Q&A\
**Tags:** calculations, feature-request, Business-Intelligence-Engineer, quick-sight\
**Created:** [February 8, 2024, 9:36pm UTC](https://community.amazonquick.com/t/calculated-field-size-limit-issue/25723 "2024-02-08T21:36:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![naaishwa1](https://avatars.discourse-cdn.com/v4/letter/n/cdc98d/32.png) [@naaishwa1](https://community.amazonquick.com/u/naaishwa1)\
**Post date:** [February 8, 2024, 9:36pm UTC](https://community.amazonquick.com/t/calculated-field-size-limit-issue/25723/1 "2024-02-08T21:36:24Z")

</div>

I’m trying to update an existing calculated field. When I hit ‘Save’ I get the following message?  
Calculated fields size limit exceeded  
This action could not be performed because the overall size of the calculated fields is too large. To resolve this issue, try removing some calculated fields or reducing the size of calculated fields.

In this particular analysis, I have a another calculated field with the same calculations that I’m able to save with no issues. Additionally, I’m also able to create new calculated fields with smaller calculations.

How is the size of the calculated fields determined? Is it determined on the dataset/analysis level or per calculated field level?

---

<div class="post-metadata">

**Author:** ![olivia](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/olivia/32/6060_2.png) [@olivia](https://community.amazonquick.com/u/olivia)\
**Post date:** [February 9, 2024, 4:09am UTC](https://community.amazonquick.com/t/calculated-field-size-limit-issue/25723/2 "2024-02-09T04:09:57Z")

</div>

Hi @naaishwa1,

There is a calculated field size limit which applies across all calculated fields (hence why you could previously create longer calculated fields and can now only create smaller calculated fields).

This is currently a hard limit, I would recommend if possible removing any unneeded calculated fields or moving these calculated fields down to your dataset layer.

I have tagged this as a feature request to be reviewed by the product team.

---

<div class="post-metadata">

**Author:** ![Kellie\_Burton](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/kellie_burton/32/2603_2.png) [@Kellie\_Burton](https://community.amazonquick.com/u/Kellie_Burton)\
**Post date:** [February 12, 2024, 5:11pm UTC](https://community.amazonquick.com/t/calculated-field-size-limit-issue/25723/3 "2024-02-12T17:11:49Z")

</div>


