Link to URL - Encoded URL (not working)
Answered
Hi,
I've got a Link to URL field with a custom parameter.
Custom parameter: http://uniqueurl.com
Field: /goto/homepage
Result: http://uniqueurl.com%2Fgoto%2Fhomepage
I was hoping there was a way it didn't get encoded and just turned straight into a link.
Any ideas?
Hi James,
Thanks for reaching out. I've come across this behavior once with another client but unfortunately was unable to replicate the issue. It may be worth attempting this in a different browser. Alternately, the solution in the aforementioned case was:
"so I have worked out another way to achieve what I want - essentially join to the Configuration table in YF config database and get a custom parameter value with the Base URL. This way I can update the url via the Yellowfin GUI and it will update through the links in the reports."
I'm happy to re-attempt replication here, but I do recall spending a decent amount of time trying to replicate this previously, and we wound up just coming up with another solution to get the end goal as I simply wasn't running into any encoding issues. In terms of attempting replication, can you please let me know what version/build of YF you're on and what browser you're using?
Thanks,
Mike
Hi James,
Thanks for reaching out. I've come across this behavior once with another client but unfortunately was unable to replicate the issue. It may be worth attempting this in a different browser. Alternately, the solution in the aforementioned case was:
"so I have worked out another way to achieve what I want - essentially join to the Configuration table in YF config database and get a custom parameter value with the Base URL. This way I can update the url via the Yellowfin GUI and it will update through the links in the reports."
I'm happy to re-attempt replication here, but I do recall spending a decent amount of time trying to replicate this previously, and we wound up just coming up with another solution to get the end goal as I simply wasn't running into any encoding issues. In terms of attempting replication, can you please let me know what version/build of YF you're on and what browser you're using?
Thanks,
Mike
Hey Mike - I went back with our developers and we also came up with another option which was basically to create a new field with the clients base URL and then concatenate the fields at the view level with freehand SQL (then format as URL). It works for what we need so it's okay for us.
In case it helps, we are on 8.0.3 of yellowfin and i was using chrome (didn't actually try with a different browser).
Hey Mike - I went back with our developers and we also came up with another option which was basically to create a new field with the clients base URL and then concatenate the fields at the view level with freehand SQL (then format as URL). It works for what we need so it's okay for us.
In case it helps, we are on 8.0.3 of yellowfin and i was using chrome (didn't actually try with a different browser).
Hi James,
Thanks for providing this information, and happy to hear you've found a suitable method to reach your end goal! Unfortunately, I still can't replicate or really even think of a plausible reason why the links encoding would change.
Considering this seems to be sorted now though, please let me know if you have any additional questions on this. I should add that if this becomes an issue for you again down the road, or if you want to pursue this further anyways, we can explore other possibilities, such as receiving a copy of your config db, should that be possible, and seeing if we can replicate locally with that. Either way, please let me know.
Regards,
Mike
Hi James,
Thanks for providing this information, and happy to hear you've found a suitable method to reach your end goal! Unfortunately, I still can't replicate or really even think of a plausible reason why the links encoding would change.
Considering this seems to be sorted now though, please let me know if you have any additional questions on this. I should add that if this becomes an issue for you again down the road, or if you want to pursue this further anyways, we can explore other possibilities, such as receiving a copy of your config db, should that be possible, and seeing if we can replicate locally with that. Either way, please let me know.
Regards,
Mike
All good on our end for now. Thanks Mike!
All good on our end for now. Thanks Mike!
Hi James,
Thanks for confirming! Please don't hesitate to reach back out should you have any more questions or concerns.
Regards,
Mike
Hi James,
Thanks for confirming! Please don't hesitate to reach back out should you have any more questions or concerns.
Regards,
Mike
Replies have been locked on this page!