Parameter Not Recognized in Calculated Field for Dynamic SVG Display

Question & Answer
, ,
1

Hi everyone,

I’m encountering an issue in AWS QuickSight where a parameter (info_tenantalias) that I’ve set up is not being recognized correctly within a calculated field. My goal is to display different SVG logos based on the value selected from a dropdown control linked to this parameter.

Setup:

  1. Parameter: I created a string parameter named info_tenantalias.
  2. Control: I added a dropdown control linked to this parameter with values numobile and kogan.
  3. Calculated Field: The calculated field I created looks like this:

sql

Copy code

ifelse(
  ${info_tenantalias} = 'numobile', 'https://example.com/client1-logo.svg',
  ${info_tenantalias} = 'kogan', 'https://example.com/client2-logo.svg',
  'https://example.com/default-logo.svg'
)
  1. Custom Content: I’m using this calculated field to dynamically display an SVG image in a Custom Content visual.

Problem:

  • I receive the error: “Parameter info_tenantalias is missing in expression.”

What I’ve Tried:

  • I’ve double-checked the parameter’s existence and linkage to the control.
  • I re-created the parameter and control to ensure there are no configuration issues.
  • I’ve also tried different syntax approaches but still encounter the same issue.

Question:

Has anyone experienced a similar issue or can provide insights on why this parameter might not be recognized within the calculated field? Are there alternative approaches to dynamically display content based on a parameter in QuickSight? Any guidance would be greatly appreciated!

2

Hi @Kokka,

Did you give your parameter a default value? It needs to have a default value before you can use it in a calculated field.

1 Like
3

Hi @Kokka,
It’s been awhile since we last heard from you. Did you have any additional questions regarding your initial topic or did David’s response help for your case?

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

Thank you!

4

Hi @Kokka,
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 topic in the community and link this discussion for any relevant information that may be needed.

Thank you!