Forum Discussion
- DeanOusterhoutQrew Assistant CaptainWould an "=" sign in the password field cause issues?
- DeanOusterhoutQrew Assistant CaptainMystery solved... sort of... the = was causing the problem. Is there a way to escape special characters like the = in a password?
- _anomDiebolt_Qrew EliteUse %3D for =.
I don't know what language you are using but every modern language has a URLEncoding function. If you URL is coming from the QuickBase formula language you use this:
URLEncode([url]) - DeanOusterhoutQrew Assistant CaptainThanks Dan. I am using powershell... I will lookup the urlencode.
- _anomDiebolt_Qrew Elite$Encode = [System.Web.HttpUtility]::UrlEncode($URL)
$Decode = [System.Web.HttpUtility]::UrlDecode($Encode)
Do us a favor and post your script when it is debugged.
- DeanOusterhoutQrew Assistant CaptainI decided to not use the authenticate and use the usertoken instead. instead of the xml, I used the URL approach, and for that I was having issues with the multiple records being handled by QB. It kept coming back and saying 1 record input, regardless of how many were included.
The solution involved adding a carriage return after each data row ("'r'n "). Then I had issues with strings, but encapsulating them in double quotes fixed that.
Saga over for now... :) Thanks for the help Dan.