ContributionsMost RecentMost LikesSolutionsRe: RESTful API temp user tokensI had made the same assumptions as you did on the temporary authorization scopes but while testing it today I had the same issue. Temporary authorization tokens for application DBIDs are not accepted for queries on child tables. I have been avoiding the REST API for my code pages because I didn't want to deal with the extra API calls and state management for the temporary authorization tokens but I see now its even messier than I had assumed. I love the REST API and user tokens specifically for my server and desktop applications but I keep falling back on the XML ones for code pages. ------------------------------ Nathan Hawe ------------------------------ Re: Convert Multi-line Text to multiselect text using line breaks as delimitersThat's a pretty cool solution, actually. We've used direct barcode reading into text boxes to populate fields before but that's a clever use of the multi-select field and form rules for validation. It might be clunky but it does work. ------------------------------ Nathan Hawe ------------------------------ Re: Convert Multi-line Text to multiselect text using line breaks as delimitersI tried your exact setup there with Split([Field],"\n") and that worked as expected. I did that on Windows in Chrome and on Mac with Safari and both instances worked. In both instances I typed directly into the multi-line text field and the split resolved after I saved the record. Are you copying a block of text from some other application that could be using a different encoding for line feeds such as "\r"? ------------------------------ Nathan Hawe ------------------------------ Re: Uploading HTML to QuickBase with REST APIThere's an older XML API endpoint that can add/update pages https://help.quickbase.com/api-guide/add_replace_dbpage.html. I think this would work well in your situation, you'd just have to change the way you make requests to this specific endpoint to match the XML requirements. You can still use user tokens for most of these older XML APIs by passing it in a "usertoken" tag so you shouldn't need to authenticate differently. Some people have used this to make deployment tools for code pages in the past. I haven't used this personally, but looking at the code might be helpful https://github.com/cullenjett/quickbase-cli. ------------------------------ Nathan Hawe ------------------------------ Re: Setting Time Stamp with API_EditRecord Using Epoch MillisecondsI believe that's the expected behavior. The milliseconds value doesn't include any time zone offset information so it makes sense to treat all values as UTC. The API will accept a string format like MM-dd-yyyy H:mm to update date/time fields which can be a bit easier to generate in UTC especially in JavaScript where you have UTC specific methods on Date objects. let d = new Date(); let formattedDateString = `${d.getUTCMonth()+1}-${d.getUTCDate()}-${d.getUTCFullYear()} ${d.getUTCHours()}:${d.getUTCMinutes()}` ------------------------------ Nathan Hawe ------------------------------ Re: Edit EOTI app record I've got to second Black Harrison's comment here. It sounds like you're creating a publicly accessible database of people's names, passport numbers, and possibly health information. ------------------------------ Nathan Hawe ------------------------------ Re: URL edit record through email You might be able to hack something together that has the same effect using a code page. If you pass whatever parameters you're using in the API call to the code page instead, you can read those parameters when the page loads and then construct and redirect to your API call. Since your code page is not the API endpoint, Quick Base will redirect unauthenticated users to the login page first. For example, your new link might look like domain.quickbase.com/db/<dbid>?a=dbpage&pageID=<pageid>¶m1=X¶m2=Ywhich your code page will then redirect to what you're currently using likedomain.quickbase.com/db/<dbid>?act=API_EditRecord&_fid_6=X&_fid_7=Y. One strategy for extracting query parameters in JavaScript: http://stackoverflow.com/a/979995 ------------------------------ Nathan Hawe ------------------------------ Re: Soap XML handling That's understandable. Hopefully a pipeline user will see this and offer their insight. As for your API question, the short answer is that APIs don't talk with other APIs. You would write a script that bridges the two. For example, you would have a script that makes a call to your SOAP endpoint, parses the XML response, and then uses the parsed XML response to create a new request to Quick Base. You can do this with any combination of APIs regardless of response type since it's the script that does the translating. Pipelines are effectively doing the same thing but abstracting the coding/hosting which is why they're comparatively more limited in what they can do. That's not to say they don't offer value; just that there are tradeoffs for either approach. ------------------------------ Nathan Hawe ------------------------------ Re: Soap XML handlingThis doesn't really answer your question and I hope somebody with more expertise in pipelines might have some better advice for you, but my personal suggestion would be look into using the Quick Base API directly if you have any programming experience. I've found that writing my own integrations using the API has been faster, more reliable, and easier to maintain than attempting the same in pipelines. ------------------------------ Nathan Hawe ------------------------------ Re: multiple jquery calls - first is working but the two following aren't pulling full dataThat's difficult to say since all of the integration with Quick Base is obfuscated by those calls to your PHP files. I'd suggest testing that your PHP endpoints give you the properly formatted JSON response you expect and then continue debugging from there. ------------------------------ Nathan Hawe ------------------------------