Jump to content

beaverq

Members
  • Posts

    14
  • Joined

  • Last visited

  • Days Won

    1

beaverq last won the day on May 12 2016

beaverq had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

beaverq's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. OK--my last reply is too complex. I really just need to know why I don't get a proper XML return like appears in the API and what I need to do to get it. I showed the code in my first post. Is there something wrong with it? I think I followed the API example very closely. Thanks.
  2. So how come I'm not getting anything but a dump? Regardless of what combinations of the last four parameters I use, I keep just getting a dump: all the valued bunched together with no delimitation at all. I've studied that API, so please don't just quote the API at me. That's what I'm basing my efforts on. It doesn't tell me anything but just gives circular definitions: that is, the definition basically repeats the same words that are in the term it's trying to explain. That's no explanation. What's the difference? I need to know what "RAW" mode and "AUTO" mode are. The API doesn't say, as nearly as I can tell. And I don't get any different results when I change these parameters.I also get this kind of error message from Firebug on Firefox on occasion--not always (most recently when I tried "true false false false" for the last four parameters: Do you have any idea what it signifies? Thanks.
  3. OK, that makes sense for SelectDataRaw. I'm guessing I could just have an array of field names (depending on which I needed to get) and then somehow programmatically link that array with the returned array of values. But I would still like more info on using SelectDataXML. 1) Why don't I get an XML-like output the way it's shown in the Web Services API document? Why do I just get either a dump without even comma delimiting or nothing or some error? Changing some of the values in the last four parameters doesn't seem to make any difference in the output I get. Do I have to do something specific with these to get the XML-like output? Or do I need to treat the return differently with my code? 2) Regarding the four last parameters, I wasn't so much interested in the general theoretical understanding as in what different they make in the query--that is, how one decides which settings to use. What difference would each of these make when set as 'true' vs when set as 'false'? And, does the 'right' setting for one of these parameters depend on what the others are set as? Thanks.
  4. I'm having trouble with the WS 'SelectDataXML' call. With the 'SelectDataRaw' call, I get stuff back as a comma-delimited dump, but just the values, not the field names. I was hoping with the XML call to have both, but as I tinker with the various options, at most I get only a dump of the values without any field names and, at worst, strange errors. This is the code snippet: $client = new SoapClient($wsdl); //raw /* print_r($client ->SelectDataRaw($bridgeAccount,$profile,$password,"initialscandata1",false,"", "License_No = '12345'","","","")); } */ //XML $result = $client->SelectDataXML($bridgeAccount,$profile,$password,"initialscandata1",false,"", "License_No = '12345'","","false","true","false","false"); echo $result; } So my main question is, can someone give more direction on how to use the 'SelectDataXML' to get what I need (or a better way to get back an associative array with both field names and values)?A second questions concerns the four parameters at the end of the call (IsSchema, IsRaw, IsElement, IsBase64). The WebServices API simply gives circular definitions of them. Can someone give a more complete explanation of what they are and when and how to use them--or else direct me to where they might be more thoroughly explained? Thanks
  5. In the middle of a project, on Monday morning I suddenly was unable to log into the Caspio Bridge from my Linux box, which had been working fine up to that point. The Caspio compatibility page (http://www.caspio.com/login/systemcompatibility/) says: It still says that this morning. However late Monday I received word from Caspio that they had dropped support for Linux browsers, supposedly because they hadn't passed their "Quality Assurance tests." This was probably part of the "upgrade" they announced in the mailing that came out late Tuesday, "Resolved Caspio Bridge Performance Issue." Since Caspio hasn't deigned to notify the Linux world of this change, maybe this post can save others from losing a full day's work figuring out what the heck is going on. Whether you choose to find a Windows box to work on or find a more compatible DB host is up to you. My lost day included long phone and instant chat conversations with Caspio support people who apparently had no clue that this change in support was why I could no longer log into Caspio.
  6. One more stupid gotcha: Even if one is using a variable ($email) in the Caspio WS call, one needs the extra set of quotation marks. $email = "generic@somemail.com" won't work. It needs to be $email = " 'generic@somemail.com' ".[btw]
  7. We didn't want to be doing our validation (see following thread, "accessing external web service from Caspio") on the web page. (Since the web service is an alien domain, we'd have to combine a proxy server action with the Ajax call anyway.) And the more we thought about it, the more we realized there is nothing in the Caspio DB that could directly kick off a WS call to some other WS. So we're using php on our web server: -with PHP get or check a field in the Caspio DB with the Caspio WS. -with PHP, make the call to the validation WS. -with PHP, write relevant info back to the Caspio DB with the Caspio WS.
  8. My bad. Turns out "SSL support is not available in this build" refers to the PHP build I'm using. After a bunch of poking around I discovered that there's a separate SSL module for PHP and that openSUSE doesn't install it with the rest of PHP. Once I added that, this particular problem disappeared.
  9. You know, all the time I wasted trying to figure out the undocumented features of this product, I could have build my own LAMP project 3 times over. Just by chance I discovered the answer to my query. I was trying to enter an email address with an UpdateData query and got this error message: "multipart' immediately suggests a possible need for quotation marks, so I experimented with entering the ValueList item as "'generic@somemail.com'" and lo-and-behold, it worked. Weird. A string within a string?Anyway on another hunch I tried putting one word into the ValueList field: and I got the same error message that this thread started with (the strange message about "Invalid Column Name"). And putting the double set of quotes (" 'bread' ") removed that error message and let the UpdateQuery work.I'm beginning to believe that this ridiculously incomplete "API" for the WS is just put out there to trap people into needing their $250/hour coding services. :x
  10. Can anyone explain this: when I do a "SelectRawData" call to Caspio DB with the web service I get strange results depending on what I do with the "Criteria" field. --if I use field "Customer", which is an autonumber field, the query runs fine. --if I use any other field (eg, "LastName = Jones"), I get this strange error message: Why would the ws try to treat the field content (Jones) as a column name (LastName)? (Trying to put single quotes around 'Jones' doesn't seem to help.)The WebService API documentation says that the SelectRawData call Criteria field is an SQL 'where' query without the 'where'. As far as I know, this is a valid SQL query: Select age from tblStuff where LastName = "Jones"
  11. I'm trying to use the PHP models provided by Caspio to pull data from my database. I get this error message: "Fault faultcode: HTTP, faultstring SSL support is not available in this build". I've checked the properties of the web service profile and the "Require SSL encryption" is definitely not checked. What else could be causing this error? What is the error message referring to with "in this build"? Thanks. beaverq
  12. Has anyone kicked off a web service from an embedded datapage call to capture one or more data fields to go into your database? If so, any suggestions as to how to do it?
  13. We need to do this: 1. Collect data for first page with embedded Caspio datapage form. 2. When user moves to next page (or, in some cases, the next field on the form), we need to be authenticating, from an external web service, the data entered on the page or field just exited (while user is entering the next piece/set of data). --Check with external web service to authenticate the info (eg, make sure the entered address is a USPS deliverable address and put the address in proper USPS format) --Edit the Caspio record with the cleaned up data. Or--if the data doesn't validate (eg, a non-deliverable mail address)--create a "flag" so that when the entry pages are finished, we can go back to this page and get better data. 3. Etc. for each new "page" of data. So the question is: Is there a way to build a "trigger" into the Caspio DB that will access the external web service and run the authetication and data update automatically? Is this something we would use Caspio Web Service for? If not, what's the best way to do this (architecturally)?
×
×
  • Create New...