New fields are not visible in the joined dataset

[realhema]

I’m working with two Direct Query datasets in Amazon QuickSight:

• Dataset A: recently updated with new fields
• Dataset B

I’ve joined these datasets using a LEFT JOIN on Sauron ID. While I can see the new fields when querying Dataset A directly, these fields are not appearing in the joined dataset results.

Details:

• Both datasets are using Direct Query mode (not SPICE)
• The join condition appears to be working correctly for existing fields
• The new fields are visible in the source dataset query results
• The new fields are not appearing as options in the joined dataset

I’ve already verified that:

• Both datasets are up to date
• The join condition is correct
• I have appropriate permissions

Has anyone encountered this issue before? How can I make the new fields visible in the joined dataset?

[Xclipse]

Hi @realhema

Welcome to the Quick community!

When using Direct Query datasets, data automatically refreshes when you open the associated dataset, analysis, or dashboard, and filter controls refresh every 24 hours. However, structural changes to the schema, such as adding new fields in the source dataset, are not always auto detected by Quick in joined datasets. To reflect schema changes like newly added fields, you need to manually edit the dataset to add fields and save it, do the same for the joined dataset.

Quick caches metadata and requires you to refresh or edit the dataset to update its schema metadata. This can be done by manually editing the dataset in the dataset editor and including new fields.

Please refer to the below documentation this might be helpful for you.

Refreshing data in Amazon Quick Sight - Amazon Quick Suite

Questions about efficiency, costs and usage of Spice vs. Direct Query in Quick Sight

Hi @ArthurMendes SPICE (Super-fast, Parallel, In-memory Calculation Engine) is Amazon Quick Sight’s in-memory engine designed for faster performance by preloading data. SPICE is more efficient for performance because it stores data in memory, resulting in low-latency queries and better scalability for large datasets. It’s cost-effective if your queries are run frequently and you want to avoid paying for every query separately. Direct Query connects to your data source in real-time, allowing u…

[WLS-Luis]

Hi @realhema,

Following up here as it’s been a while since last communication took place on this thread; Were you able to see Xclipse’s most recent response and/or find a solution yourself in the meantime?

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

Thank you!

[realhema]

Thank you for following up! Yes, I learned that fields were hidden in Excluded Fields section. I was able to remove them from excluded fields section.