ChristineKirk
Qrew Trainee
Joined 2 years ago
User Profile
User Widgets
Contributions
Extrapolating nuanced data
Hello again - one more for today! I'm self-taught in Quickbase and data management altogether. I'm trying to suss out the best way to pull some data. We capture a dataset on consults in our Quickbase. Every call our program receives, gets one record entered into Quickbase. Sometimes callers call us back for more than one consult on the same case. To this end, we have a field capturing "New consult" or "Continuation of consult". Then we capture services performed and patient demographics of the consult.... many situations can transpire in which we got that data on the first call, or on a subsequent call, and it's quite varied (for instance, first call may be very brief, they give us limited info and say they'llc all back/we don't get that info right then, but do on the longer subsequent call; the inverse of that, they call, we spend meaningful time, capture the data the first time, and they call back for some follow-up questions). Now, to extrapolate services (how many times did X happen on a case we consulted on) -- how can I pull that nuanced data out? I guess I can manually look through the data, which is how we do indeed do this to report quarterly on how many cases we served..... There must be a better way to look across the life of our program and pull the data.11Views0likes0CommentsQuickbase - Jumping into managing someone else's build-out
Hi all! I'm just looking for some beginner/intermediate wisdom. I am taking on the (to me, much coveted) task of managing and revamping Quickbase across other arms in my division. This'll be the true test of whether I'm actually cut out for this haha - it's one thing to be self-taught and know how to build and fix across the empire thatI'vebuilt, but another to jump into someone else's empire. So. Looking for some wisdom: What things should I know when going in and offering up a "revamp" of sorts? What major pitfalls should I watch out for? How might one approach doing this sort of thing? My first approach has been to learn about what sorts of things they use Quickbase for today, what data is captured, what they'dliketo use it for down the line, and then with that, I'm peeking in the back end, seeing what fields/forms/reports exist, and wrapping my head around how it all is (or isn't) working together today A sub-set of questions - might it behoove us to build several apps? I honestly have no idea how much Quickbase costs our organization, if it's per app, per user, some combination. That all is tightly managed at a level higher than me in our IT department, and app managers are only that - we're not "App Owners". But I've been thinking it really might behoove us to have several apps, that are all cross-linked, because for instance, each unit in our division coudl really have several tables -- as my unit does. There are things that will be division-wide, such as inventory management; but if we lump all these tables into one app, it will get pretty messy pretty quickly. So my sense is the best thing to do would be propose having several added apps that can be connected, one "Master" app where the universal tables live, and one for each division's division-specific work.10Views0likes0CommentsRe: Relationships functional question
Thank you! Okay yes, that is where I've seen that transpire is if I changed a field to multi-select (including formula multi-select text). My predecessor seems to have done what you're mentioning and set it to Maximum Date from the child. I don't know what then is misfiring on that field..... in one example, it produces 11-13-2023 as the "latest record" - and is supposed to be summarizing a specific field, which is "Date of Service". On that exact example, both the Date of Service on the child table AND the newest record were created on 11-14-2023. I'm not sure why the 1 day discrepancy. The function here is supposed to be: Parent Table = Community Organizations Child Table = Our program's outreach to those organization Ideal field = Renders the date of the latest outreach onto the parent table, whichcouldbe the record date, but most accurately is pointing to the date the staff entered as "Date of Service/Outreach"20Views0likes2CommentsRelationships functional question
Hello! Intermediate-level user here and very much enjoyed the former QB forum - hoping to see some familiar faces on here. I am dipping my toes in the waters of fixing a Quickbase app that I didn't actually build - which is great! Something I'm thinking I want to learn more about/perhaps pursue from here. But also feels like the litmus test here - fixing my own Quickbase that I built is one thing, but now getting to know the ins-and-outs of someone else's is - wow. Anyway. One ask from the team I'm refreshing this for, I'm struggling with because I'm not sure this is possible. They want to see on the Table view, a field that populates a date from the related table of the last record. Perhaps there's a formula that I can pull to make this a field. So -- in the simplest terms, I feel like what this field needs to be is: Parent Table owns the field, and that field is points to the Record Date of the newest Child Table record. How can I do this? Is there perhaps a formula field to build? Also - I see my predecessor attempted this, and it is reporting out on several fields..... I don't quite know how to make sure my fix populates everywhere, other than editing the specific existing field. Could I just copy that field, and it'll still report on those records? I know if I "change type" of field, you can often only do that once, and it won't let you change it a second time.55Views0likes5CommentsSave & Keep Working/Required Fields
Hi all! I posted last week but am really stumped still. Some of my end users are requesting to save information while still working on a new record -- and in our workflow, it's common that they may be gathering datapoints over multiple hours (and sometimes in 15 minutes). They don't want to lose their datapoints as they complete collection - and we don't want to miss any of our required fields, which are critical to a number of areas from regulatory requirements to funding support. Someone suggested that I "hide" a section that has the save button and add the conditions on that my required fields must be filled in to show that section, but the save button is actually always present, so that doesn't quite achieve what I'm hoping for. Additionally, we have some layered requirements - if X is "Yes", then require 4 other fields. So I'm just trying to figure out the best possible approach to letting them save their progress, while not relinquishing control over getting those required fields. Any suggestions are most graciously appreciated! ------------------------------ Christine Kirk ------------------------------6Views0likes2Comments"Save as" and required fields
Does anyone know if there's a way (or do you have alternative suggestions) to ensuring "required fields" do get completed at a record close-out, but that Quickbase is setup in such a way that the end user can save their progress as they go? For context - my program provides consultations that can sometimes be 4+ hours; users are asking for a way to begin inputting their datapoints without risking losing those datapoints as a record sits there open/waiting to be saved and closed out - but I do want to be sure on final closeout, we have received those datapoints, many of which are required by our grant funders, and for the user's own payroll of course, so it's vital to get that info at the time they're completing the new record. Thanks! ------------------------------ Christine Kirk ------------------------------1View0likes1CommentRe: Using a formula field to open a record in another form
Oh that is interesting! We really only have those two forms (and I'd LOVE to build the "Logistics" form into something that just pulls directly into a child table without having to pull in each individual linked field (there are probably 50 or so linked fields). Maybe a default form could be basically two buttons - to launch either of the two other forms, based on what you're needing. Confidentiality Notice: This e-mail, including any attachments is the property of Trinity Health and is intended for the sole use of the intended recipient(s). It may contain information that is privileged and confidential. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please delete this message, and reply to the sender regarding the error in a separate email.1View0likes0Comments