Forum Discussion
SterlingLong1
6 years agoQrew Trainee
Ok, I'll start by saying I should not have mentioned the https thing, it's simply a requirement by QB Webhooks that I found a little annoying. Not super important.
The bigger issue is to follow, let me see if I can give a better example. With some pictures.
Alright so if I do this:
If I do this (Using the constant that you helped me make Mark), pulled in from another table:
Where the contents of [TestURL] are www.googe.com/
I end up with this error from the webhook:
Quickbase URL encoded the field. Which I can understand being necessary in the body, and necessary in URL parameters.
I hope this makes more sense of my problem, sorry I was too vague before. I've been thinking about this for a while so I just kind of assumed it would be easy enough to understand.
The URL encoding seems to happen automatically. There is no code here, no javascript, etc. Just me trying to use a field and its contents as a URL. Which seems to go against intended purposes.
Using a field as a URL isn't necessary. It simply allows me to ensure that all the URLs are the same by using that one field, and if the endpoint URL ever changes, I just have to change it in my constant... It makes upkeep much simpler. All the thing are simpler with this.
Let me know your thoughts, and if anything doesn't make sense let me know.
I should note that it does this when the field is both type text and URL. That has no effect. The URL encoding still happens in the same way.
------------------------------
- Sterling Long!
------------------------------
The bigger issue is to follow, let me see if I can give a better example. With some pictures.
Alright so if I do this:
And type out the URL completely, then the webhook works perfectly and can ping google. Google is an example here.
If I do this (Using the constant that you helped me make Mark), pulled in from another table:
Where the contents of [TestURL] are www.googe.com/
I end up with this error from the webhook:
Quickbase URL encoded the field. Which I can understand being necessary in the body, and necessary in URL parameters.
I hope this makes more sense of my problem, sorry I was too vague before. I've been thinking about this for a while so I just kind of assumed it would be easy enough to understand.
The URL encoding seems to happen automatically. There is no code here, no javascript, etc. Just me trying to use a field and its contents as a URL. Which seems to go against intended purposes.
Using a field as a URL isn't necessary. It simply allows me to ensure that all the URLs are the same by using that one field, and if the endpoint URL ever changes, I just have to change it in my constant... It makes upkeep much simpler. All the thing are simpler with this.
Let me know your thoughts, and if anything doesn't make sense let me know.
I should note that it does this when the field is both type text and URL. That has no effect. The URL encoding still happens in the same way.
------------------------------
- Sterling Long!
------------------------------
MarkShnier__You
Qrew Legend
6 years agoI think we have reached the end of my technical ability to make suggestions. Maybe somebody else will chime in.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
- SterlingLong16 years agoQrew TraineeK, again, thanks for all your help Mark! I really do appreciate it =) The constants idea works beautifully.
------------------------------
- Sterling Long!
------------------------------