Using variables in API URL requests
Im having trouble getting the API to post the value of the field instead of the literal text name of the field. What am I doing wrong? Obviously I am new to this. It creates the new record in the ...
Forum Discussion
MarkShnier__You
Qrew Legend
Qrew LegendI forgot to explain URLEncode. When doing successive calls, you just have to use that crazy nested format. Can't explain why, you just do.
But when putting values into a field and those values may have spaces or special characters, (For example [Sage - Vendor] might be a Vendor name I suppose), then it needs to be URLEncoded to make it a valid string which will be able to navigate the great unknown magic of the internet and get back to your table. Ever notice, for example, that in all your time wasted surfing the net, that no URL ever had a space in it? Well there are also other illegal characters, so the URLEncode allows those special characters to get through the internet.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
Thank you so much Mark! I wasn't expecting an answer midnight Saturday but was happy to get it. It works, although I cant get the redirect to work for some reason. QB is telling me I need a semicolon at the end of the variable declaration, but its there. Anyway Ill sort that out later. Thanks again!
- MarkShnier__You
This line was missing the closing quote after the 10=
& "&_fid_10=" & URLEncode([Sage - PO Number]);
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------