Quick_BaseJunki
Qrew Captain
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: Bringing attention to the End of Life for Webhooks
Adding my take (previously shared with Quickbase directly). At this point, we (the developer community) do not feel there is parity between table webhooks and pipeline webhooks. I would say the top 3 reasons are: Access: Not all users have access to Pipelines or it's often easier to create table webhooks with shared access which is not currently an option in Pipelines. Speed: Table webhooks run faster than you can blink even for large sets of data. Bulk Triggers: Today a table webhook triggered off a bulk action (grid edit or import) creates a single trigger that can either be used to create a single action like add record OR a bulk action with ImportFromCSV. In pipelines any time a bulk action (grid edit or import) triggers a pipeline it files individually which can cause issues with large updates that may trigger 1000+ instances. Here are some feedback cases on this particular issue: https://feedback.quickbase.com/app/#/case/359112 https://feedback.quickbase.com/app/#/case/160597 Since the retirement of Automations I've found myself relying more heavily on table webhooks when the use case is simple and the above are necessary. Without parity it would be DISASTROUS and expensive to rework the apps where extensive table webhooks have been used... and I'm sure many partners feel the same. In addition to the above, I agree with others who have also mentioned the often painfully slow process of building Pipelines compared to the speedy development of table webhooks as well as the difficulty searching and organizing Pipelines. -Sharon ------------------------------ Quick Base Junkie Sharon Faust https://quickbasejunkie.com ------------------------------Re: Pipelines - Outlook Events
The event body should be able to accept HTML in which case you could add something like this: <a href="https://yourcompany.quickbase.com/db/tasktableid?a=dr&rid={{a.id}}">Link to Task</a> you'll need to replace the "yourcompany" with your realm name and the "tasktableid" with the 9 digit table ID for the Task table. You can change the label "Link to Task" to whatever you want the link text to be. {{a.id}} is the reference to the Task Record ID# which I assume is in step a. Let me know if that works! -Sharon ------------------------------ Quick Base Junkie Sharon Faust https://quickbasejunkie.com ------------------------------Re: ifv not working with API_AddRecord?
Without seeing the full formula, I think what you may be looking for is: ?a=nwr in place of where you have ?act=API_AddRecord The API_AddRecord happens behind the scenes and requires a redirect to say what to display after the new record is created. However, since the record isn't created at the time the button is pressed there is no way to capture the new record's ID to display it in the the redirect. There are some ways of doing this, but they are quite complex. Using nwr (or API_GenAddRecordForm) simply passes the values you want to a new record but the user is responsible for saving it. This means you will still need a custom save button on your form when using the ifv=10. I teach both APIs and Rich Text buttons in the Quick Base Junkie Button Bundle if you want to learn more. -Sharon ------------------------------ Quick Base Junkie Sharon Faust https://quickbasejunkie.com ------------------------------Re: Help with creating a multidimensional chart
This may help with the comparison to the prior period. Super Easy Year Over Year Chart by Month In terms of displaying those 3 different metrics, I would suggest a dashboard (like Chayce described) with 3 reports and a filter by the AM as needed. Or if you have an account manager table, you could add the 3 reports to their record (no relationship to the other tables needed just a report link). -Sharon ------------------------------ Quick Base Junkie Sharon Faust https://quickbasejunkie.com ------------------------------Re: Have Vibrant Colors nevr worked on mobile?
@Mike Tamoush Absolutely you'll learn this and SO much more about buttons in The Button Masterclass. That's also a great tip for the 100% width. Here is the rich text formula for that black button. Basically, it uses the Vibrant class but then layers style elements for the color, shape, etc on top. var text STYLE = "background: black;" & "border-radius: 20px;" & "white-space: nowrap;"; var text URL = "https://quickbasejunkie.com"; var text LABEL = "Visit Quick Base Junkie"; "<a class='Vibrant SaveBeforeNavigating' style='" & $STYLE & "' href='" & $URL & "'>" & $LABEL & "</a>" ------------------------------ Quick Base Junkie Sharon Faust https://quickbasejunkie.com ------------------------------Re: New forms- code
@Ryan Doble The <> that you see in the menu is not to access the code. It is only to format text as code so the browser doesn't interpret it as code (which is the opposite of what you want it to do). It's the same as if you were using <code></code> in the HTML... basically useless in my opinion. For me, this is a HUGE gap in the new vs legacy forms. Please give this feedback to Quickbase. -Sharon ------------------------------ Quick Base Junkie Sharon Faust https://quickbasejunkie.com ------------------------------Re: Have Vibrant Colors nevr worked on mobile?
@Mike Tamoush It's been that way. I have a course called The Button Masterclass where I compared how buttons display on desktop vs mobile (app, safari, and chrome) based on the different ways you can display a button. What you are describing would be the orange button in this image which uses the Vibrant Alert class. Mobile does not have the same style sheet as desktop so the Vibrant classes are not loaded. ------------------------------ Quick Base Junkie Sharon Faust https://quickbasejunkie.com ------------------------------Re: New Forms - Mobile support
@Rick Putnam That is correct. I recently had the same question. In this video from Empower (starting at 8:10), they talked about them and the beta at the end of the year. -Sharon ------------------------------ Quick Base Junkie Quick Base Junkie https://quickbasejunkie.com ------------------------------Re: Rolling 3 Month Average
@Adam Keever This is a cool use for query formulas. You may want to consider using the AdjustMonth() function to create the 2 month earlier date for the query. So, var text QUERY = "{7.OAF.'" &AdjustMonth(FirstDayOfMonth([Bill Creation Date]),-2) & "'}AND{7.OBF.'" & LastDayOfMonth([Bill Creation Date]) & "'}AND{9.CT.'TEXT_STRING_FILTER'}"; SumValues(GetRecords($QUERY),18)/Size(GetRecords($QUERY)) -Sharon ------------------------------ Quick Base Junkie Quick Base Junkie https://quickbasejunkie.com ------------------------------
