Sheet tooltip in pivot table with parameters

Q&A
,
1

Hello Everyone,

I came across the below issue while creating sheet tooltips for pivot visual.

The pivot visual has rows, columns and values. The columns has a calculated field which is based on parameter selection. E.g.: if parameter = region , then the columns has to display region and if parameter=country, then the columns has to display country.

In sheet tooltip page, I used this calculated field in a table. But when I saw the actual pivot table, the tooltip was not shown.

Can anyone confirm if this is a limitation or am I missing something?

image
image401×248 6.7 KB

Thanks,

Kripa

2

Hi @Kripa,

Sheet tooltips are supported on pivot tables (Sheet tooltips announcement), so the issue is likely related to your parameter-driven calculated field, not a general pivot table tooltip limitation. The error you’re seeing (“Your calc field expression contains invalid syntax”) points to the calculated field failing to resolve in the tooltip sheet context.

A few things to check:

  1. Parameter availability: Make sure the parameter your calculated field references exists and is accessible from the tooltip sheet. If the tooltip sheet can’t resolve the parameter, the calculated field will throw a syntax error.

  2. Calculated field syntax: Double-check your expression. For a parameter-driven column switch, it should look something like:

ifelse(
  parameter = "region", regionField,
  parameter = "country", countryField,
  NULL
)

Make sure the parameter name and field names are correct and that all fields referenced exist in the dataset used by the tooltip sheet.

  1. Field type consistency: If your calculated field switches between fields of different data types (e.g., one string, one date), this can cause errors in certain contexts.

  2. Tooltip sheet dataset: Ensure the tooltip sheet’s visual is using the same dataset that contains the calculated field and has access to the same parameter.

Here is the documentation for Tooltips: Tooltips on visual types

If you have any additional questions, feel free to reply.

Hope this helps!

3

Hi @WLS-Cesar ,

I believe the parameter driven calculated field is right. I checked everything and it looks correct to me. I have shared arena link Sheet Tooltip Pivot. Could you help me this? I have created pivot table with parameter driven calculation and a sheet tooltip too.

Let me know if anything is required .

Thanks

4

Hi @Kripa,

Thanks for sharing the sandbox link, I went through it and I agree that your calculated field looks correct. I tried replicating this in both the sandbox and in a different environment and as long as a calculated field is included in either the table or tooltip, you will get the “Your calc field expression contains invalid syntax.” error.

I believe I found a possible workaround:

Create 3 pivot tables on the same sheet:

Pivot Table A (Sub-Category):

  • Rows: Category

  • Columns: Sub-Category

  • Values: Sum of Sales

Pivot Table B (City):

  • Rows: Category

  • Columns: City

  • Values: Sum of Sales

Pivot Table C (State):

  • Rows: Category

  • Columns: State

  • Values: Sum of Sales

Then you can use hide and show logic on each pivot table so that Pivot Table A only shows when Param = “Sub-Category”, Pivot Table B only shows when Param = “City”, and Pivot Table C only shows when Param = “State”. This way, only one pivot table is visible at a time based on the user’s parameter selection.

Create 3 matching tooltip sheets (one per pivot table):

  • Tooltip Sheet A: Table visual with Sub-Category and Sales

  • Tooltip Sheet B: Table visual with City and Sales

  • Tooltip Sheet C: Table visual with State and Sales

Assign each tooltip sheet to its corresponding pivot table.

This may not be ideal, but I believe this should replicate the functionality that you’re seeking.

Hope this helps!

5

Hi @WLS-Cesar ,

Thanks for sharing the workaround and I will try and get back.

But I also want to know that is it a limitation in Quick to use sheet tooltips where it has parameter driven calculations?

6

Hi @Kripa,

First, I wanted to reach back out and see if Cesar’s workaround was able to assist with your use case.

Second, in regard to your most recent question, I would say that it is possible that this could be a limitation or even a bug/error (since your calculated field logic seems correct), so I would definitely recommend creating a support ticket, as AWS Support will be able to further see if either is indeed the case. Please help the community by following up in general within the next 3 business days!

Thank you!

7

Hi @Kripa,

Since I haven’t received any further updates from you, I’ll treat this inquiry as complete for now. If you have any additional questions, feel free to create a new post in the community and link this discussion for context.

Thank you!