Bug Report: Incorrect HYPERLINK Function Behavior in Looker Studio

[montibo]

Dear Looker Studio Support Team,

I am writing to report an issue with the HYPERLINK function in Looker Studio. When using the HYPERLINK function within a CASE statement to display dynamic links, the expected behavior is not achieved. Instead of displaying the specified label as a clickable link, the label is concatenated directly with the URL, resulting in incorrect link formatting.

**Steps to Reproduce**:
1. Create a calculated field using a CASE statement that incorporates the HYPERLINK function.
2. Define conditions where, based on the input, the HYPERLINK function should generate a clickable link with a specific label.
3. Observe that the output concatenates the label with the URL, rather than displaying the label as a clickable link.

**Expected Outcome**:
The label should appear as a clickable link directing to the specified URL.

**Actual Outcome**:
The label and URL are concatenated, resulting in improper link formatting.

**Impact**:
This issue affects the usability of reports that rely on dynamic link generation, leading to potential confusion for end-users and a less interactive reporting experience.

I have found a workaround by restructuring the formula to avoid using the CASE statement directly with the HYPERLINK function. However, this requires additional logic and complicates the report design process.

Thank you for your attention to this matter and I hope you enjoy this bug! 

Best regards,

Thibault Montoya

[lauratilton · Accepted solution]

I have found that it is best not to include any sort of calculated field within HYPERLINK. You'll want to create the URL and Label values in separate fields, then bring them together with HYPERLINK.

[ta74]

how can we fix this

[montibo]

Thanks for the reply. This is a good solution. Actually, I did a bit different . I used hyperlink only as a main function and then put all my conditions into the hyperlink functions. It worked. However, I think they should consider as a bug even though there is a workaround. thanks a lot.