Total values not shown, piecharts and tables

[cosorio]

We have noticed some unusual behavior:

• Null categories: We have observed that the “others” category is being labeled as “null”.
• Missing totals in pie charts and tables: Total values are not being displayed in pie charts and tables, which is affecting data visualization and analysis.

This behavior occurs in visuals using data from Snowflake, as we are currently transitioning from Redshift to Snowflake.

[Giridhar.Prabhu]

Hi @cosorio

Your screenshot shows the dates (months) projected on the pie chart. Null may indicate data that did not have a date attributed to it.

Can you try a simple pivot table visual by filtering the mfecha_rem (the date field) for the null values and bring in the other dimensionsal details to pin point to the problem and then see what drives the null values?

I don’t specifically think it is a Snowflake issue. Must be something in your dataset definition.

[cosorio]

Hi @Giridhar.Prabhu,

The screenshot also shows the filter applied. Here are a few key points to clarify:

• No null values: I’m fully certain that there are no null values in the date fields or in any other fields.
• Issue persists with different datasets: This visual is for reference purposes only, but using different datasets and combinations of fields, we are receiving the same result.
• Pivot tables: The pivot tables do not show null dates because there are no null values. Additionally, pivot tables do not have an “others” category, which is why we believe the “others” category is being displayed as “null” in the pie charts.
• Screenshot details: I’m attaching a screenshot of the pivoted table where you’ll see that the total value is not shown. On the side, I’ve also included a KPI with the same operation, which should be reflected in the pie chart.
• Behavior across different datasets: Please keep in mind that this behavior occurs with various datasets. We’ve tested it with many different datasets and fields. When the datasets are hosted on Redshift, the behavior is correct. The issue only arises when using the same dataset, but allocated in Snowflake.
  
  

[Giridhar.Prabhu]

Hi @cosorio

Since you have established that the issue happens across datasets and only when it is with Snowflake I suggest you reach out to AWS through a ticket.

I thought replicating the issue in Arena was an option to look into the issue but we may not have the Snowflake database to use. So, it is better be raised with AWS for a solution.

[Brett]

Hi @cosorio,
It’s been awhile since last communication on this thread, checking in to see if you had any additional questions? As Giri suggested, you can create a support ticket here.

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

Thank you!

[Brett]

Hi @cosorio,
Since we haven’t 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!