# Missing fields in Extended Support Dashboard

**URL:** <https://community.amazonquick.com/t/missing-fields-in-extended-support-dashboard/48668>\
**Category:** Q&A\
**Tags:** admin, quick-sight\
**Created:** [July 30, 2025, 3:14pm UTC](https://community.amazonquick.com/t/missing-fields-in-extended-support-dashboard/48668 "2025-07-30T15:14:25Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![jkrewquicksight](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@jkrewquicksight](https://community.amazonquick.com/u/jkrewquicksight)\
**Post date:** [July 30, 2025, 3:14pm UTC](https://community.amazonquick.com/t/missing-fields-in-extended-support-dashboard/48668/1 "2025-07-30T15:14:26Z")

</div>

Missing fields in Extended Support Dashboard:

In Extended Support Cost Projection, the last visual in the RDS Extended Support (Cost Projection) shows as “Fields for this visual no longer in analysis”.

There are two missing fields available. I believe the missing fields are account\_name and rds\_name, since similar fields are available in EKS and OpenSearch tabs.

Is there an update for this dashboard that addresses these missing values in the rds\_extended\_support\_view Athena view?

 ![Screenshot 2025-07-30 at 11.11.31 AM](https://d1wl4jav5dp96l.cloudfront.net/original/3X/8/2/82b762f7a502deaa3a9b30f544f558a0df271b37.png)

---

<div class="post-metadata">

**Author:** ![Xclipse](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/xclipse/32/20455_2.png) [@Xclipse](https://community.amazonquick.com/u/Xclipse)\
**Post date:** [July 30, 2025, 6:58pm UTC](https://community.amazonquick.com/t/missing-fields-in-extended-support-dashboard/48668/2 "2025-07-30T18:58:24Z")

</div>

Hi @jkrewquicksight

Welcome to the Quick Sight community!

Could you please check whether the missing column(s) in your analysis are currently part of the excluded fields list in your dataset?

Whenever changes are made to a dataset, such as adding or removing fields, it’s important to follow these steps to ensure they reflect properly in the dashboard:

- Save and publish the updated dataset after making any changes.
- Reopen and republish the analysis to apply those updates.
- Finally, verify that the visuals use the updated dataset fields accordingly.

This process ensures your visuals won’t show “Fields for this visual no longer in analysis” due to outdated field mappings.

---

<div class="post-metadata">

**Author:** ![jkrewquicksight](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@jkrewquicksight](https://community.amazonquick.com/u/jkrewquicksight)\
**Post date:** [August 7, 2025, 9:09pm UTC](https://community.amazonquick.com/t/missing-fields-in-extended-support-dashboard/48668/3 "2025-08-07T21:09:25Z")

</div>

Thank you for your suggestion. I’ve confirmed that the fields are not excluded.

I believe the problem is the setting of ManageCUR2|no per the CloudFormation related to Deployment in Global Regions ([Deployment in Global Regions - Cloud Intelligence Dashboards on AWS](https://docs.aws.amazon.com/guidance/latest/cloud-intelligence-dashboards/deployment-in-global-regions.html)).

We are not yet using CUR 2.0 data for our main dashboards (CID, CUDOS), and I’m not yet ready to migrate.

I believe CUR 2.0 must be required for the RDS extended support resource level dashboard widget? I’m not certain this is the issue - all data is showing for OpenSearch and EKS dashboards.

---

<div class="post-metadata">

**Author:** ![jkrewquicksight](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@jkrewquicksight](https://community.amazonquick.com/u/jkrewquicksight)\
**Post date:** [August 7, 2025, 9:30pm UTC](https://community.amazonquick.com/t/missing-fields-in-extended-support-dashboard/48668/4 "2025-08-07T21:30:12Z")

</div>

In eks\_extended\_support\_view View, the following block refers to details such as account\_name and cluster\_name:

FROM  
preprocessed\_eks\_clusters\_inventory  
WHERE (collection\_date = max\_collection\_date)  
)  
, eks\_clusters\_usage (billing\_period, usage\_date, payer\_account\_id, linked\_account\_id, account\_name, region\_code, cluster\_name, k8s\_version, item\_description, usage\_unit, resource\_id, original\_usage\_type, usage\_amount) AS (

Looking in the rds\_extended\_support\_view, I don’t see any similar references that would join account\_name or rds\_name.

I’m wondering if the issue is that I’m not leveraging CUR 2.0, or whether my rds\_extended\_support\_view can be modified.

---

<div class="post-metadata">

**Author:** ![Xclipse](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/xclipse/32/20455_2.png) [@Xclipse](https://community.amazonquick.com/u/Xclipse)\
**Post date:** [August 8, 2025, 4:46am UTC](https://community.amazonquick.com/t/missing-fields-in-extended-support-dashboard/48668/5 "2025-08-08T04:46:32Z")

</div>

Hi @jkrewquicksight

Sorry, I’m out of ideas. I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a [support case](https://docs.aws.amazon.com/awssupport/latest/user/case-management.html). If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!

---

<div class="post-metadata">

**Author:** ![Xclipse](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/xclipse/32/20455_2.png) [@Xclipse](https://community.amazonquick.com/u/Xclipse)\
**Post date:** [August 23, 2025, 10:25am UTC](https://community.amazonquick.com/t/missing-fields-in-extended-support-dashboard/48668/6 "2025-08-23T10:25:51Z")

</div>

Hi @jkrewquicksight

It’s been a while since we last heard from you. If you have any further questions, please let us know how we can assist you.

If we don’t hear back within the next 3 business days, we’ll proceed with close/archive this topic.

Thank you!

---

<div class="post-metadata">

**Author:** ![Xclipse](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/xclipse/32/20455_2.png) [@Xclipse](https://community.amazonquick.com/u/Xclipse)\
**Post date:** [August 27, 2025, 5:12pm UTC](https://community.amazonquick.com/t/missing-fields-in-extended-support-dashboard/48668/7 "2025-08-27T17:12:38Z")

</div>

Hi @jkrewquicksight

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

Thank you!

---

<div class="post-metadata">

**Author:** ![Xclipse](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/xclipse/32/20455_2.png) [@Xclipse](https://community.amazonquick.com/u/Xclipse)\
**Post date:** [August 27, 2025, 5:12pm UTC](https://community.amazonquick.com/t/missing-fields-in-extended-support-dashboard/48668/8 "2025-08-27T17:12:41Z")

</div>


