Link to URL formatter does not work with custom parameter at first position.
Hi,
I found a new error. This time, I wanted to format a field content as “Link as URL” (system external) in the prepare step in a view, and YF adds “http://” where it doesn't belong. The URL contains a “custom parameter” ${ShowTicket_URL}, and that seems to be the root cause of the problem.
There is a working combination (good case, but not useful):
- ShowTicket_URL (custom param) = fqdn/example/
- ID Link (view field) =
=> result: https://fqdn/example/<field content>, the structure is correct, the link works.
But if I want to use the full power of the custom parameter, the protocol has to be included in the parameter (bad case)
- ShowTicket_URL (custom param) = https://fqdn/example/
- ID Link (view field) =
=> result: http://https://fqdn/example/<field content>, the structure is wrong
My technical expertise tells me that YF is constructing the URL in the wrong order here
- check if it is a valid URL
That doesn't seem to be the case with a ${ at the beginning, so YF adds a "http://" as a prefix
btw: why not HTTPS? We also use YF with HTTPS. - then YF replaces the custom parameter
This results in an unusable URL.
My analysis may be wrong, but it doesn't matter—it's still a bug.
The good thing is that it is very easy to reproduce and you can definitely recreate it in your system right away (just combine a view field and a custom parameter).
;) Stefan (YF 9.16)
The same problem 
Hello Stefan,
My name is Deepak Chaganti from the Yellowfin Technical Support Team. We have received your support request, and I will be your primary contact on the following ticket:
Ticket Number: #32826
Case Title: Link to URL formatter does not work with custom parameter at first position.
I will proceed to replicate the scenario and will provide updates as soon as possible regarding the outcome.
Sincerely,
Deepak Chaganti
Yellowfin Technical Support Engineer
Hello Stefan,
My name is Deepak Chaganti from the Yellowfin Technical Support Team. We have received your support request, and I will be your primary contact on the following ticket:
Ticket Number: #32826
Case Title: Link to URL formatter does not work with custom parameter at first position.
I will proceed to replicate the scenario and will provide updates as soon as possible regarding the outcome.
Sincerely,
Deepak Chaganti
Yellowfin Technical Support Engineer
Hi Stefan,
Yes, it appears that YF is prepending http:// when the protocol is already specified in the parameter.
In my test, I created a parameter TEST with the value https://www.myexample.com. I then used this parameter with 'Link to URL' in the report builder as $(TEST)/## (without manually adding a protocol) and saved the field. When I copied the resulting URL from the field, it appeared as:
http://https://www.myexample.com/Latin+America
I will raise this with the product team to clarify whether we should use only the domain name (without specifying the protocol) in custom parameters and why YF prepends http:// at the start.
Thanks,
Deepak
Hi Stefan,
Yes, it appears that YF is prepending http:// when the protocol is already specified in the parameter.
In my test, I created a parameter TEST with the value https://www.myexample.com. I then used this parameter with 'Link to URL' in the report builder as $(TEST)/## (without manually adding a protocol) and saved the field. When I copied the resulting URL from the field, it appeared as:
http://https://www.myexample.com/Latin+America
I will raise this with the product team to clarify whether we should use only the domain name (without specifying the protocol) in custom parameters and why YF prepends http:// at the start.
Thanks,
Deepak
Hi Stefan,
I hope this email finds you well.
I just wanted to let you know that this issue has been fixed and will be included in the upcoming YF 9.16.1 release, which is scheduled for October. I will provide you with an update as soon as I have more information.
Thanks,
Deepak
Hi Stefan,
I hope this email finds you well.
I just wanted to let you know that this issue has been fixed and will be included in the upcoming YF 9.16.1 release, which is scheduled for October. I will provide you with an update as soon as I have more information.
Thanks,
Deepak
Hi Stefan,
I hope you're having a great week.
I just wanted to let you know that this is now fixed and included in YF 9.16.1. This version has now been released and is available for download from the Yellowfin portal.
Thanks,
Deepak
Hi Stefan,
I hope you're having a great week.
I just wanted to let you know that this is now fixed and included in YF 9.16.1. This version has now been released and is available for download from the Yellowfin portal.
Thanks,
Deepak
Replies have been locked on this page!