EvanWestbrook
Qrew Cadet
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Automatically Import CSV Files
Brett, You might be able to set up a code page to handle this. I was able to find an older post here that has some sample code (link). It makes use of the File Web API (link) and Quickbase's V1 Import from CSV (link). I realize this doesn't answer your no/low code request, but it might get your started if you want to go down the code route. A user could select a file on their computer, and the code page would import it. ------------------------------ Evan Westbrook ------------------------------Re: Page Refresh to fast for automation
Andrew, I don't have a solution for you, but maybe I can help you frame your hunt for a solution. When a button is clicked in a web page, it often sends some sort of API Call. This is typically in the form of an HTTP request. What this means is that when a button is clicked, it sends a message to a server and says "do the thing." This request can have many responses from the server. For example: I did the thing I asked the server if I could do the thing and it wouldn't let me I don't understand what you said Here's the data you asked for with the thing No response Quickbase Automations are an easy way to make a "to do" list of multiple API Calls to process sequentially when an Automation receives a request to "do the thing." In Quickbase Automations, when a record is saved, Quickbase asks itself "do I need to do any things." If the answer is "yes," Quickbase sends a request to the Automation saying "do the thing." All of this comes back to your original issue since QuickBase Automations don't give a response after successfully "doing the thing." Your examples reference code or special buttons because a common way to code your use case would be: Perform action --> API call --> Wait for response --> Do next step Click Button --> Make API call --> On successful response --> Refresh page The limit of Automations in this case are that you don't have the "wait for response" stage. The Automation receives the request to "do the thing" and you trust it to "do the thing" successfully. Does your Automation only have one step? If so, you could embed the process above in a formula URL or formula rich text button by using QuickBase's API instead of Automations (Automations are just a nice UI to make QuickBase API calls). I hope this gets you closer to your solution. Let me know if you have any additional questions. Thanks, ------------------------------ Evan Westbrook PRIME Developer Harder Mechanical Contractors Inc. Portland OR ------------------------------Re: Save and next tab button
Mike, As everyone has mentioned, It looks like you have some " and ' out of order or missing in Lines 1 and 2. Make sure to remove the ">" at the end of Line 1. Left in, it will effectively close the opening of the anchor element (the <a> thing) twice. For example, if we remove all parameters, your current formula would render: <a>>Next<a/> You want it to read: <a>Next<a/> ------------------------------ Evan Westbrook PRIME Developer Harder Mechanical Contractors Inc. Portland OR ------------------------------Re: Save and next tab button
Mike, SaveAndNextTab.js is a code page. The rest of the code blurb is in a "Formula - Rich Text" field. Regarding debugging, try the following: Make sure your field is "Formula - Rich Text." In Rich Text, we're making a button using an anchor element instead of letting QuickBase do it for us through a URL field. Your original syntax looks "Formula - URL"ish. That might result in a QuickBase syntax error. Hover over the button in QuickBase and look at the bottom left corner of your browser window. This will give you a preview of the code that will execute on click This is helpful verifying what QuickBase is actually making with the formula. Make sure everything looks correct there. javascript execution in QuickBase is very strict when it comes to no spaces. Correct Syntax Result Incorrect Syntax Result (special character trimmed everything after "getScript(") Open the developer tools of your browser (F12), access the Console, and watch it when you click the button. If there is a JavaScript error or something isn't working as expected, an error will often appear in the console log. If all else fails, could you attach a screenshot of the syntax error? Is it in the QuickBase field or the JavaScript page? I'm interested to see your solution. Maybe there's an App Setting I'm missing. Thanks, ------------------------------ Evan Westbrook PRIME Developer Harder Mechanical Contractors Inc. Portland OR ------------------------------Re: Save and next tab button
Mike, I was able to adjust your provided code to make a working feature with a Rich Text field. Here's the working code: var text customButtonScriptOne = "<a href=javascript:$.getScript('https://YOURREALM.quickbase.com/db/YOURDBID?a=dbpage&pagename="; var text customButtonScriptTwo = "');void(0);"; $customButtonScriptOne & "SaveAndNextTab.js" & $customButtonScriptTwo & " class='Vibrant' style='color:white; background:#427cd8; white-space:nowrap;'>Next</a>" Note, I had to switch some of the " to ' and vice versa for this to work in Rich Text. Syntactically, yours would have worked in a .js page. I can't speak as to why your code stopped working, but I was able to identify a few potential syntax errors. Updating these allowed the feature to work in my app. No "=" after "pagename" (Line 1) Extra anchor element closing bracket (Line 1) No need to surround "javascript...void(0);" with single quotes. This may have caused some wires to get crossed when it comes to " or ' Potentially redundant () surrounding "javascript...void(0)" By the way, this button is a really cool feature. Thanks for sharing it here. Thanks, ------------------------------ Evan Westbrook PRIME Developer Harder Mechanical Contractors Inc. Portland OR ------------------------------Re: Webhook + json issue with multi-record updates
Bo, I found your post when I was trying to figure this out, and I wanted to share my solution. %repeatOn% and %repeatOff% loops through all records that were updated and applies anything between those values. For example: // Sample Data: // Records = 1, 2, 3 // Input 1 %repeatOn%"[Record ID#]"%repeatOff% // Output 1 "123" // Input 2 %repeatOn%"[Record ID#] and "%repeatOff% // Output 2 "1 and 2 and 3 and " If you wanted to send the same JSON object for different records, you could use %repeatOn% and %repeatOff% to build an array of JSON objects: // Input [ %repeatOn%{ "newStatus": "[Implementation Status]", "newNote": "[Status Notes]", "QuoteProdID": "[Id]" },%repeatOff% ] // Output [ { newStatus: "Active", newNote: "foo", QuoteProdID: "1" }, { newStatus: "Inactive", newNote: "bar", QuoteProdID: "2" }, ] This would also work for building an array nested inside a JSON object: // Input { "newStatus": "[Implementation Status]", "newNote": "[Status Notes]", "QuoteProdID": [%repeatOn%"[Id]",%repeatOff%] } // Output { newStatus: "Active", newNote: "foo", QuoteProdID: [ 1, 2, ] } I hope this helps! Thanks, ------------------------------ Evan Westbrook PRIME Developer Harder Mechanical Contractors Inc. Portland OR ------------------------------Re: Relationships - Parent, child and proxies
Rory, Making Registration a parent of Transfers would create the architecture required for the summary field. It sounds like you're looking for is something like: Transfer Added Find a Registration that matches the Transfer's [Telephone Number] Write the Registration's [Record ID #] to Transactions [Related Registration] I'm not aware of a native QuickBase function that will accomplish Step 2 (search then add.) However, you might be able to get users to make that connection for you without even knowing it: Create relationship of Registration to Transfers (one to many) Make [Telephone Number] the proxy field for [Related Registration] Make [Related Registration] required On the Transfer table, make this new [Telephone Number] the way users select [Telephone Number] for a Transfer When a record is saved and [Related Registration] changes, copy new [Telephone Number] to old [Telephone Number] field This can be accomplished via Form Rule, Webhook, or Automation In your UI, always display old [Telephone Number] and only allow users to edit new [Telephone Number] By using this method, the actual [Telephone Number] receiving the Transaction is preserved (valuable for audit purposes). The Registration also stays tied to this Transaction even if Registration record's [Telephone Number] changes. As a bonus, this will make sure your users are always making Transfers to valid Registrations. After all, they're already entering [Telephone Number]. They might as well use the method that ties everything together! You'll also save your users some clicks (1 click and 10 keyboard presses goes to 2 clicks)! ------------------------------ Evan Westbrook PRIME Developer Harder Mechanical Contractors Inc. Portland OR ------------------------------Re: Large Number Rounding Up Past 10 Million
Curtis, I don't have an answer for you, but I found some additional information. Maybe someone from the QuickBase team can help clarify because I'm curious about this, too. QuickBase Function documentation does mention there are some issues inherent with rounding and floating point numbers I replicated your problem with a hard coded number. When my number when from 1,000,000.50 to 10,000,000.50, QuickBase actually changed my formula. Check it out below: ------------------------------ Evan Westbrook PRIME Developer Harder Mechanical Contractors Inc. Portland OR ------------------------------Re: Open a record automatically in edit mode
To add to Mark's solution: If you want the record to open in edit mode, you can use the following: URLRoot() & "db/" & [_DBID of the child table] & "?a=er&rid=" & [Record ID# of child with maximum date] The only difference is that the user is being sent to the "edit record" (er) form instead of the "direct record" (dr) form. ------------------------------ Evan Westbrook PRIME Developer Harder Mechanical Contractors Inc. Portland OR ------------------------------
