HarrisonSmith
Qrew Trainee
Joined 6 years ago
User Profile
User Widgets
Contributions
Auto-Logout
Did QB recently (within the past few months) make any updates that would impact a user being auto-logged out due to inactivity? Admittedly this hasn't happened to me as I spend a big chunk of my day in QB, but I've had a lot of users complain that they've been getting logged out more and more often. Apparently they used to go the entire day without getting logged out (despite our realm-level policy being set at 2 hours of inactivity before triggering a log out), and now they're reporting as little as 30 minutes of inactivity before being asked to log back in again. It's a mild annoyance that's impacted a lot of my users. Something I never really noticed because I hardly go 20 minutes without using QB during work hours, but maybe our 2 hour logout policy at the realm level wasn't being enforced properly and now it sort of is?38Views1like2CommentsRe: Pipeline Design for Bulk Record Updates
interesting, thanks Mark. Sounds like I misunderstood the purpose of the bulk event step. So for updating thousands of records all at once, it's still easiest/most performative to just have the pipeline loop through all the records one at a time (outside of leveraging Sharon's self-created methodology)?107Views0likes4CommentsPipeline Design for Bulk Record Updates
Hi all. I have a timecards table where users track all the things they're working on. Relatedly, we have a separate child timecard table, with a narrower field list but otherwise the exact same records. This was done a while ago to reduce volume on long term storage of these records because we hit the table limit of 500 MB. So anytime a timecard record gets created or edited in the parent table, there's a pipeline that checks to see if the record has any related child timecard records. If not, it creates a new child timecard record with all the relevant fields populated. If there is already a child timecard record, it updates that child record with all the newest field values. Then as the last step (only for new timecards), updates the newly created child timecard record with the Related Parent Timecard value so it's easy to verify all timecards have exactly 1 child record. Other than being resource-intensive, this pipeline works perfectly fine most of the time. However, twice/month, we export all our timecards to another system outside Quickbase, which is tracked with a date and checkbox field being updated via Find & Replace in a report to prove they were exported. The problem is, there are often around 5,000 records being updated simultaneously. When that update occurs, with so many timecards being updated all at once, a queue builds up that can take hours for the pipeline to process and update all of the underlying child records. Beyond general performance issues, users are often still creating new timecards, which don't show up for a while in the child timecard table because those new timecards are now in the back of the line to be created/updated. I want to redesign the pipeline using the On New Bulk Event step, so these records can be processed, created/edited all at once so a queue doesn't build up and take hours to finish running and cause confusion amongst end users. What's the best way to go about that? I tried replacing the trigger from an On New Event to an On New Bulk Event, while leaving everything else about the pipeline the same, but if anything, it's taking even longer than before.199Views0likes6CommentsBar Chart based on Multi-Select Text field, but without unique combinations
Is there a good way to show the # of records where each option from a multi-select text field is selected WITHOUT showing every single unique combinations. For example, if Option A is selected on one record, Option A AND Option B would NOT be a separate bar on the bar chart, it would just show the actual choices in the field.71Views0likes1CommentRe: Convert Email Lookup Key to Text
yeah I've tried converting both and either field toText while leaving the other as is. It always comes back to that same issue of expecting a textlist, despite the email field not being a combined text or anything like that. Its just a normal email field if(toText([Primary Matter Contact - Email]) <> "", [Primary Matter Contact - Email], toText([Referring Troutman Attorney (ref) - Email Text]))69Views0likes1CommentRe: Convert Email Lookup Key to Text
Sure. When I entered what you had above, it says I can't use <> on types text or textlist. The formula field is already a formula - email field, though I've tried with both formula email and formula text to no avail. if([Primary Matter Contact - Email] <> "", [Primary Matter Contact - Email], [Referring Troutman Attorney (ref) - Email Text])75Views0likes2CommentsConvert Email Lookup Key to Text
I feel like I'm going insane this should be extremely easy. I'm trying to make a formula email field that simply gets populated with 1 email field (primary contact) if that's in fact filled out. Otherwise, populate with the referring attorney email field value. Both are lookups from two different tables. The email field for the referring attorney lookup is the key field for that table. For some reason QB is expecting a textlist, not text. I've tried all sorts of type conversions, as well as part/split functions (since Split is what comes up under Textlist Functions, though the email field would never have more than a single value in the first place). I know this is going to be ridiculously simple in the end.193Views0likes6CommentsAdd Existing Child Records from New Parent Record
I have an app where people can have many related child documents. Now, the app requirements have expanded, so that documents can belong to many people. I want users to be able to select multiple existing people records when they create a new document record and uploading the file attachment, basically like a multi-select text field but for existing soon-to-be child records. I'd prefer to avoid creating a many:many assignments table for the sake of simplicity but if I have to then I have to. Any ideas?100Views0likes1Comment