Name: App Adventures: a tips & tricks treasure hunt
Uploaded: 2025-02-27T19:46:04.662Z
Duration: 56 min 36 s
Description: App Adventures: a tips & tricks treasure hunt

Transcript for "App Adventures: a tips & tricks treasure hunt": Hello, everybody, and welcome to our session today, App Adventures, a tips and tricks treasure hunt. Today's session is gonna be a little bit different from normal. What we're basically gonna do is there is a recording that we have from Empower Pro where we're going to be pulling down, basically a bunch of awesome examples that they covered in Empower Pro. There's an app that goes along with it. I'm gonna drop a link in it to the chat right now. So if anyone wants the chat the, app themselves to follow along, you can take a minute to add it to your account. You can also always find it if you need it in our docs. There's a little tiny, option for docs in the upper right hand corner above the chat. That'll give you a link to a bunch of different topics including the app. So don't worry if you don't wanna download it today. You can always download it in the future. Also, this session will be available on demand after I wrap up. So if there's anything that you wanna come back to, watch it yourself, watch it at your own time, you'll have plenty of time to do so. I'm gonna let's say we can give people another minute or two to funnel in, and I see a bunch of folks already saying hi in the chat. I hope you're all having a great day so far. We're so we'll let people funnel in for a little minute or two, and then we'll get rolling on the recording. While the session is running, I will still be here answering questions, so please feel free to put them in our q and a section, which is right next to the docs. Or we'll have another q and a section at the very end where we can go through any questions folks have left or anything that people wanna cover, after they've had some time to absorb all of this information. It's a lot to cover, so it's it goes it can go a little fast. Let's see. While we're waiting for a few more folks to funnel in, just wanted to give everyone the reminder, we have Empower twenty five coming, up soon for the first time in several years since before the pandemic. We're doing live Empower again. It'll be March 31 and April 1 in, New Orleans. Registration is still open. Folks could either use this QR code that's on the screen right now to learn more about the registration, see the agenda starting to go up, or anytime you need to, you can just look up Quickbase Empower, and you'll be able to find our registration page too. This is just my, plug for if you are really looking for an opportunity to get deeply into Quickbase, meet a bunch of other folks who are excited about it just like you. It's a great opportunity to network, chat, learn about Quickbase. We haven't seen you all in a very long time in person, so we're all looking forward to it. Alright. So it looks like we've got a pretty good group going. So what I'm gonna do is I'm going to start the, recording. Like I said, if anyone has questions during the course of the session, please feel free to drop them in the q and a or the chat, and we'll make sure to either cover them while while everything's running or we can get to the at the very end of the q and a session that will be live so that everyone can get through cover any questions. Otherwise, I hope you enjoy the session. So as you all know, we're gonna find some treasure in our applications. Now couple of things that we are going to go over today, for the agenda. We're gonna talk about making our apps a little bit more user friendly, maybe discover some methods, to enhance your applications that you already have or maybe just give you ideas for future applications. There might be some settings or features that can improve your application. I'm gonna call them buried treasure, hidden somewhere in the settings of Quickbase that maybe you never noticed before or could use. And there are also some, you know, tips and tricks to fine tune some apps for optimal performance. So we are going to do, seven hands on activities today with a treasure application. I'm going to just use these slides for a couple, and then it's gonna be all hands on from there. So a little bit of fun here. And I do have a couple of notes before we begin. So, if you have a builder account, feel free to log in to that. You don't necessarily have to use your builder account. You can use corporate accounts if that's okay with your, your teams. If you have a question, put it in the chat. Tracy and I are gonna do our very best to answer your questions. She's gonna be moderating chat for me and helping you guys out. Now the important thing here is that to please use a Chrome browser window if it's at all possible. One of our activities requires that you do need to use a Chrome browser window. K? So that's what I'm gonna be using for our activities, and I would suggest that you do the same. So if everybody is ready, go ahead and drop something in the chat, some type of emoji, whatever your favorite one is, and we're gonna get going. So now the first thing we need to do is download our app from the Exchange. So I'm gonna hop out of my slide and right into my builder program. This is just what I'm using here. So if you are in your my apps page or, you know, anywhere in your application, you can click the waffle menu in the top left corner, and we're gonna go to the exchange. K. We are going to search for treasure as we are doing with our application today. And we're gonna go ahead and download that. So if you never use the Exchange, all you have to do is click onto the app, click the blue install button, and you can keep the name of it if you want. I personally like to put the date in front of my application so I know when it was used and when it was downloaded. Not something you have to do, but just what I do. And go ahead and click install. Might take it just a second or three seconds here. Alright. Once you get the green success, you can go ahead and click the blue open app button. And I'm gonna go ahead and exit out of my exchange tab so I don't have too much going on at the top of my screen. Alright. Hopefully, everybody's got your application downloaded. Now notice we do have four tables in this application. We have treasures, expeditions, museum loans, and documents. Now this application is tracking all of our treasures that we find on our expeditions that we go on. We have amassed a very large collection of treasures, and we, being so generous, loan these out to museums for them to put on display, show, or anything like that. So That's what our application is doing for us today. Now the one here that we do need to access quickly is the documents table. So let's go ahead and go to documents really quickly. Now in here, you will see the deck that I am using. Great thing for you to download, especially because at the end of the deck are some additional nuggets and pieces of treasure that we're not gonna do hands on today, but little cool tips that maybe, you might not know about. It's a great thing to download. If you just click the blue link, it will automatically download to your computer. The step by step is what I'm gonna be going off of today to go through the steps of our activities, so you can certainly download that and follow along with me if you would like. CSV file. Go ahead and download that. We are gonna need that for one of our activities towards the end. And then the other two are just images that you do not need. So the first three, you can go ahead and download. So I am just going to download the CSV. I already have the other two files. And we can hold to that onto that CSV for later. Alright. Now let's hop right into our activities. Our first activity or a piece of hidden treasure that we are gonna do, you wanna follow along with me. I'm using the step by step. I'm on page one right now. So we're gonna do a little bit of finding and replacing in records. So let's go ahead and go to our treasures table. I'm gonna collapse my side panel just so you can see a little bit better. Now first thing you immediately notice is the jewelry is highlighted red. Right? So anybody know why it's red? Any guesses in the chat? If you scroll through, you'll see jewelry is red. You'll also see that scepter is red. Yeah. It's misspelled. It's not a valid valid selection. Perfect. Wonderful, guys. So just to show everybody what we're talking about, I'm gonna go to the field properties of type and just take a look at the multiple choice options that we have here. We do have scepter and we do have jewelry, but it doesn't match the spelling of the information that we imported into our application. So what we're gonna do is find and replace to correct all of those records at one time. I'm gonna click cancel to go back to my table of treasures. Now to find and replace in a certain set of records, you could filter your table report to bring up just a certain set of records, but we only have 24 here, so not a big deal. I'm gonna go ahead and click the more actions or the kebab as I call it. Either one is fine. And we're going to find and replace in these records. Now these records are specific because let's say we have a hundred records and it was only showing as 24. It would only find and replace in the 24 records that we're reviewing. K? Alright. Find and replace in these records. First thing he wants to know is what field do we want to find and replace in? Well, we wanna find and replace in type. We want to change jewelry. I spelled it the way it's done there. We wanna change jewelry with two l's to jewelry with one l. K. We don't have to worry about match whole field only or match case. And then we wanna click next. So it's saying, hey. You were gonna replace treasure replace jewelry in nine records. Sounds good to me. Let's go ahead and click replace. And important here, it does note you might wanna refresh the report window to see these changes. So once you find and replace, you can go ahead and exit out of your little window there. And let's refresh to see that hopefully jewelry is no longer red and then does not. This just saves you from having to go record by record to, you know, click a drop down or, you know, change everything in different windows. Now we're gonna do the exact same thing to also fix Scepter. Right now, it's spelled with an r e, and we wanna change it to Scepter with an e r. So we're gonna follow the exact same steps that we just did. Go ahead and click the kebab or the more actions. And if you feel comfortable, go ahead and go for it. We're gonna change it in the field type. You wanna change sector to sector. Same as before, I'm gonna click next. We're only gonna edit two records this time. That's perfectly fine. And we're gonna replace. Repeat the steps. Refresh. And now we are good to go with our find and replace in these records. Now Scepter is no longer red. Okay. Just a couple of limitations on this. Like I said, this has to be done on a table report. And just to note that this will only work on records that the user that is performing the action has the permission to modify. So if they didn't have permission to modify the records, that find and replace wouldn't work. So no worries on permissions there. Alright. Everybody good with that? If so, we are gonna move right on to hidden treasure number two. Now if you're following along with me, we're now on page two of the step by step. So the next, hidden treasure we're gonna find in our application or create is going to be a snapshot field. Now a snapshot field, if you've never heard of one or never used one, is a, a noneditable field that grabs the value of a lookup field when a child record is created. So for this example, we would like to snapshot the current value of a of a treasure. I saw Tracy's name in the chat. It made me giggle. We're gonna replace sorry. We're gonna snapshot the value of the treasure at the time that a museum loan record was created. So, you know, let's just use this Mars receptor here. If it's worth $18,000 when we loan it out and then we get it back, it was destroyed or broken, but, you know, now the current value is $25,000. Well, we might wanna see what it was when it was loaned compared to what it is now. So let's go ahead and start setting that up. We are gonna go to our museum loans table because we want to know when the museum loan was created. Now the first thing we have to do is create a field for us to be able to put that snapshot of value in. So I'm gonna go to settings, and we're gonna create a new field. Now an important thing about this is that it does need to match the same field type as the value you want to snapshot. So for this one, I wanna know the, value at time of loan. So that's what I'm gonna title this. And this is gonna be a, a currency field. It's the only field we need, and we are gonna add fields. I agree. Snapshot fields are so underutilized. Totally agree. So once we create our field, now we need to edit our field settings. If you scroll down in field settings, we just click on the name of the field, scroll down. Under advanced, you will see an option for a snapshot. It says get this field's value from a lookup lookup field and don't allow the value to change. That's exactly what we want. Go ahead and click the checkbox. For lookup field, once you click the drop down, you will only see fields that have the same field type as what matches the field you just created. So currency currency. Here we have current value. That's perfect. That's exactly what we wanna see. Now this initialize field for existing records, if you were to click this, this would run and, insert a value into the snapshot field for all existing records. That's depending on your use case, if that's something you want to do, I used it yesterday and it was perfect for my use case, then you could definitely do that. But in this situation, we're just gonna do this moving forward. K. So we're not gonna click initialize. I'm gonna go ahead and click save. Once you click save, you can click exit settings at the top of your screen. And now to demonstrate this, let's go ahead and create a new museum loan. So let's click the new museum loan at the top of the screen, and just go ahead and pick a treasure. It doesn't really matter what you pick. We can see the current value is $6,400. My museum is going to be, the Quickbase Museum. I could spell Quickbase. And we can put a date loaned in. Now, another additional piece of treasure here. If you were in a date field and you click on the letter when you tap the letter t on your keyboard, t for today, it will put today's date in. Little fun little tip. So you can do today. You can do any day you want. And let's just pick a due date. I love Halloween, so I'm gonna put Halloween as our due date. We're not gonna bother with any of the return stuff because it is currently loans. Now notice value at time of loan is blank because we haven't saved this record yet. Right? So let's go ahead and save our record after you filled out the information. Alright. Just going to view my record I just created, and you can see the value of time of loan is $6,400. Perfect. Now just to demonstrate the difference between these, now that you have your treasure here, go ahead and click the name of your treasure, and we're gonna hop back to whatever treasure you loaned out. Now let's say that the current value of this treasure has gone up. Right? I'm gonna edit our record for our treasure, and I'm gonna say this is now worth the $10,000. It's a very fancy Roman ring. One of a kind. I'm gonna save. Now here, I can just scroll down to, you know, our child records and see that it was loaned out to the Quickbase. That's exactly what I did. So I'm gonna view it with the eyeball. And just take a look at this. Value at time of loan was $6,400. Notice it did not update the current value of $10,000. That's exactly what we wanted it to do. So now if they return it to us broken, then we can say, hey. Yeah. It was worth $6,400, but now it's worth 10,000. So maybe we need to negotiate a different price for the replacement or the, reimbursement of this item. Alright. Everybody feel good with snapshot fields? Alright. Lots of thumbs ups in the chat. Love it. Okay. Moving on to hint treasure number three. This is grid edit. Right? Now I know some of you may be thinking grid edit's pretty common. Right? But sometimes, you know, you might not know it's there. So we're gonna do a little activity with grid edit. Now we are in the treasures table still. So let's hop on over to our museum loans. If you are in museum loans, perfect. But we do wanna be in the museum loans table. Now at the top of our report of all of our loans, the you can see that we have quite a few museum loans that have not been returned yet. But let's say we just got a large ship shipment of our treasures back, and I don't wanna spend the time going record by record and entering all the date returns. Right? That's where grid edit comes in. Now let's go ahead and click. There's a button directly to the right of your ad that looks like a little pad with a pencil. Go ahead and click that. Now we have a grid edit view. This allows you to populate or change multiple records at a time, and it saves them all at one time. So for this example, let's go ahead and say we got a bunch of our treasures back. Now, for this, you can go ahead and put in whatever day you'd like. So it was due in August. I'm gonna say they put gave it back in September. They returned it same as it was loaned. And for a loan rating, I'm giving them a five out of five. I would definitely loan to them again. Alright. You can grab oops. A lot of, things there. Come calendar. There we go. Just put some dates in all the way down. You can put whatever you'd like here. Now, these I'm gonna put a couple more dates in. Same as loans. Now one thing you may not know how to, exist is a fill down option. So let's say I got a lot of treasures back today. K? I can grab my field with the information that I wanna copy down and highlight down, right click, and fill down, and it will copy that same information straight down. Just saves you a lot of clicks here. All of these people returned them on the same day, and they were all the same as loans. Right? When you right click it again, you do have the option to undo fill down or you can reset to original value. So in this case, if I were to click reset to original values, it would clear it out to blank because when I access it when I accessed it, it was blank. Alright. So I'm gonna fill down again, and everybody else gets a five. You could even, enter in a note here and transcript to work with us. So it's a text field. I entered in some information on there. And now these aren't due yet, so I can leave those blank for now. If you wanna fill them in, go for it. Manchester Museum, they destroyed our Roman bust. They got a zero out of five rating. Can you pull both columns at once? Yep. Surely can. It's reset to original values. Alright. Now a couple things about grid edit. If you are grid editing on an embedded report on a parent record in your grid editing grid editing child records. If you were to try to create a new record, in the embedded report and you save it, it will create the record, but it will not link to your parent. You have orphaned records. Okay? One of my customers has a great little saying for they were having that issue with orphaned records. So on their board in their office, they have a saying that says grid edit, not grid added. Right? So you can edit your records, but adding new child records, will orphan the records, and it won't link to the parent. So keep that in mind with great edit. You could apply changes, which would allow you to keep editing. What in the world was that doing? So you can, make a whole bunch of changes, apply changes, kinda save as you go. So that way you don't, lose any of your work. And then when you're done, you just click save. Now all of our museum loans have been returned except for the ones that aren't due yet. Now, couple has a not hesitations, limitations with grid edit is, some fields cannot be edited in grid edit. So I'm gonna go back in grid edit to show you that real quick. Things that are grayed out, like the current value, the treasure type that are lookup fields, they are not editable. You cannot edit lookup fields. File attachment fields, address fields, any of those type of fields like that cannot be edited in grid edit, just fields that exist on the record and in that table. Louvre, great edit. That's cute. Adorable. Alright. If everybody feels good with great edit, looks like everybody's pretty excited about it. We are gonna move on to hidden treasure number four, which is the record title. Now for this one, we are gonna go, right here to our museum loans table, and let's pick a, a museum loan record. Doesn't matter whichever one you want. I'm just gonna click the first one that's listed here. Now at the top of your record, it says museum loan number 15. It's okay. Right? Right now it's saying it's Number 15 because that's our record ID. It's okay, but it's not very descriptive of what we're looking at. Right? So something here that might be a little bit more descriptive would be a concatenation of maybe, the museum that is at, what the treasure is, and when it's due. So we can actually change this here to a custom record title. Now it doesn't have to be a concatenation field, but that's what we did. You could just change it to one. You know, if you're on your treasures and you want your record title to be the name of your treasure, you could ax absolutely do that. Now in order to change your record title, you'll see that we already have a record title formula down here. You know, later on, if you wanted to see how we concatenated these into a formula, you are certainly welcome to go and look at the field settings and see how we did that. But for now, we are going to go into the table settings. Once you access the table settings, we're gonna go to advanced settings in the bottom left. And if you scroll down under identifying records, it wants to know what you want your record title to be. Right? Right now is our key field, which is our record ID. Not great, but it could be better. I want to change it to our field called record title, which has our concatenation in it. Right? And that's all you need to do. Pick your field that you wanna reflect in that title. Click save. Oops. Sorry about my Mac bar over here. Once you save it, let's go ahead and take a look at another museum loan. And now you can see that we have a custom record title up here. Now as you can also see, very long record titles don't work that great because it's kinda cut off, But, you do have that there. And it could just be my, screen that I'm sharing from that's cut it off a little bit, but just keep that in mind. Alright. Guys, these next two are so exciting to me. I think you guys are gonna love these if you don't know about these tricks already. So we're gonna do a little bit of magic here in this application. Let's go to our museum loans table, which we are already on. I'm just gonna click museum loans so I can go back to my default report here. Now we have our museum listed here a lot of different times. And if we were to, you know, add a new museum loan, we have to type that in just like we did with click based museum. Right? That's okay. But what happens if we need to capture more information about our museums? Like, let's say who the contact is, where it is, how many loans they've had over time. Well, we could just create a museum table and manually do all that, but not today. That's not what we're gonna do. This is the treasure that we are gonna find here. Now we would like to take this museum field and extract it into its own table. Right? So we're gonna hover over the museum name and click the kebab or the three dots for the more actions. There's an option here that says move field to new related table. Right. This is so exciting. I love this. A table name is gonna be our museums. Keep in mind, remember, our table name should be plural because these are all of our museums. I'm gonna find a nice building here for our museums. Go ahead and pick whatever icon you'd like. A single record is gonna be called a museum. Right. Description here, it just says data for the museum table. I'm gonna leave it. I'm not gonna change it to anything more specific, but you can if you'd like to. So the data will be visible, but not, but not stored in that table. It will be stored in the new table. Alright. Go ahead and click next. So even though we have 17 museum loans, we only have nine unique records. So it's gonna make a record for everything that's unique here, which is perfect. We don't want duplicates of Museum of Natural History or the Louvre Museum, anything like that. So we're good to go. Go ahead and click move field. Might take just a moment. Moment or two. It's being very slow. Oh my goodness. It's really working hard to make these nine records in the museum's table. Yes, Mark. That's that's me waiting on the screen to load. There we go. There we go. Goodness gracious. I was getting nervous. Okay. So now we have a beautifully built museums table. It extracted that information for us, made our records, and also linked all of those child records to this newly created parent. So I love doing that. I actually used this very, recently with a customer. And trying to relate this back to your own use case could be, you know, a little difficult, but, for example, they had categories in, all their records, but they wanted to report a little bit more on the specific categories. So we just took that one field, extracted it out into its own table, and it took two minutes to do that. Yes. With the link back. So if you were to click into one of the, one of the museum loan records links, you'll see that it is linked to our museum loans in the Louvre. I love all the reactions to this. I'm so glad you guys are loving this because I love that tip. It's gonna get better in the next one though. Now, if you notice, we spelled Louvre wrong. Right? Now could you do find and replace in these records before we moved it over? Sure. We could have done that. But now that we have a parent record, we just need to change it in the parent record, and it's gonna flow down to our child records. So let's go into our museum records, and I'm gonna edit L O U V R E, I believe. I think I maybe I still spelled it wrong. Hope not. L O U B R E. Yep. There we go. And save. So now we edit it edited it one place, and all of our child records are updated as well. Right. Lovely. Okay. So in that situation, we extracted one field out of a table into a new table. But what if we need to extract more than one field at a time? Now for this example, we are gonna hop over to our expeditions table. We haven't done anything with expeditions yet, but they're important because that's how we find our treasure. Right? So if you look at your expeditions table, we do have, you know, know, the name, the description. If you scroll over, we have some items about our locations. Name, description, latitude, and longitude. Now but to be honest, it'll probably make more sense to have locations in their own table because you could go to a location multiple times for multiple expeditions to find multiple treasures. Right? So we could take this, this, this, and this, all of our location related fields, and pull all four of those fields into a new related table. Alright? So the first one was a situation where you only needed one field. Now we need multiples. Now very important about this is that we do need to switch this. Well, number one, this is the, activity that you have to use Chrome for. Okay? That's number one. Number two, you have to switch it out of new style into an old style report. It only works on old style reports for now. K? I'm not sure if it'll I'm not sure for sure if it will be updated. I cannot speak. But right now, it does need to be, an old style report. So just click the toggle. It will take us to the old style report, and we would like to start with our location name. Right? So if you click the little arrow, we don't have a kebab on this one, a little arrow. We want to do new table based on this field, and that little box sometimes doesn't go away. Just click out of it. It'll go away if it, stays up on yours. Now if I were to click next now, it's only gonna allow us to pull out that one field. We want to add some additional fields to this. K. So we have five unique locations. That's perfect. If you click additional fields, we also wanna pull over the, location description. The latitude, select it and click the arrow to pull it over to the fields to extract, and longitude. We should have four fields that we want to extract all into one time. Right. Once you have location name, location description, latitude, and longitude in your fields to extract, go ahead and click okay. Looking like a table report already. Looks pretty good. Five records will be created. It's wonderful. Let's go ahead and click next. Alright. Warning. This removes the data in the columns you've specified and places it into a new table. So it does not exist in the expeditions table anymore. It's a lookup field now. K? Just warning you. If you delete the new table, then your data will be lost because it's a lookup field. Warning looks scary, but just like any normal relationship. Right? Go ahead and click continue. For the new table, we want it to be called locations, and a single record is going to be called a location. It just took the name of the field that we picked first and created that as our title, but locations and location works better. Alright. Go ahead and click continue. Hopefully, this one works faster than my museums. Yes. Tracy pointed out that this is really great for people coming from very large spreadsheets. No. Okay. Spaged and responsive. That scared me. Looks like it's maybe working. There we go. It did work. Okay. Locations. It did make our new table. I can hop out a new style now on our expeditions. And you can see our locations are hyperlinked because we have the relationship now and our description, our latitude and longitude, their lookup fields. Let's hop over to our locations table. And voila, there's all four of our fields for the location. Somebody said twenty years and still learning new tricks. That's awesome. I have used this before too, and it is wonderful. Okay. We have one more hidden treasure to find, and it has to do with merge imports. So if anybody here, and I'm sure most people have done an import in some way or done a merge import, likely, you've used the record ID as the merge field. However, that's not the only field you are allowed to use. Now, if you have the CSV for the, exhibitions from the documents table at the beginning, great. This is what we're gonna use it for. But before we get there, we have a couple steps that we need to prepare for our merge import. Now we would like to import some in more information about our expeditions. Okay? So let's hop back to our expeditions table. So what you need for a merge import, you need a field that is required to be unique. We all know record ID has to be unique. Right? And there's no option in that. But if you want another field to be your merge field, it has to be unique. So in order to make a field required to be unique, you have to go into the field settings. So for this one, we would like to make our expedition name unique. We don't want multiples that say cave exploration. We could say shipwreck dive one and two, but these are different names. So I'm gonna click the kebab and go down to field properties just to hop to it very quickly. Under basics, there's a line that says unique. Let's go ahead and check the box that says must be unique. Now if you have a lot of data and you wanna check existing entries for duplicate values, you could check that box. But we only have less than 10 exhibitions here, and we know there's no duplicate values. So no problem there. If you do have nonunique values, when you check this box and you save, you'll get a little error that says, like, We we can't save this. You I can't remember exactly what it says, but it won't allow you to save it and require it to be unique if there aren't truly unique values in there. So you would have to take a look at your, data at that point. Go ahead and save. Right. So now we have that perfect. Now we want to update, sorry, import our data. So if you have never imported before, then you are gonna click the kebab at the top of your page and then import export. From here, you have a lot of different options. We're just gonna stick with the handy dandy import table from file. Our select table, expeditions, that's great. That's what we're already in. This merge field is what we're looking at. You can click the drop down, and it will only allow you to pick fields that are unique. In this one, we made the expedition name unique, and that is perfect. This is easier because in this situation, instead of trying to put the record ID into our spreadsheet, we can match it with the expedition name. So let's go ahead and find our CSV file. I'll go ahead and open that. And those these are the only file file types you can have. Go ahead and click import from file. Alright. It's saying, hey. You're gonna maybe update some existing records. That is fine. That's exactly what we wanted to do. If you wanted to add new records, then it tells you what to do if you weren't intending on updating any existing records. I'm gonna go ahead and click okay because that's fine. K. So we have our expedition here name, name here. That's what's matching to our unique value. Here, it says, expedition description, but we have some names here. It's not exactly what we were looking for. If you click the drop down, you'll see that we don't have a field for our, lead explorer. Right? So let's go ahead and click create new field. And you can make it a text or text multiple choice. Probably text maybe makes a little bit more sense here. Same thing for this value. That is not a start date. Let's go ahead and create a new field for that one. A guest currency, that's great. That's the cost of our expedition. And our crew size. So we're gonna create new field for all these three fields. K. And someone said, they do multiple choice if they were going to be reusing the name. It's a great point. We can go ahead and make it a multiple choice. Whatever works for your use case here. But I agree with that. We can do a multiple choice because it looks like these people go on lots of different exhibitions. Now one thing Tracy pointed out to me is this link here. Oops. This link here says click here to flip this chart's orientation. Don't click it. K? She pointed out to me that if you click the that to flip the orientation, for some reason, the merge import on another field gets a little wonky. So just leave it the way it is. If you've never seen that before, you can play with that a different time, just not today. K? Don't touch. No touchy as Cisco says. Alright. You have three different import with update buttons here. Doesn't matter which one you click. Just go ahead and click one of them. Alright. It's gonna say, hey. We're gonna create three new fields. Is sure that's what you want? Yes. That's what we told it to do. Right. We had seven records updated, three fields created. Right. If you wanted to add those new fields to your forms, you could click the button. Don't really need to do that at this point. So I'm going to just go back to our expeditions table. Yeah. So now we have our information about our lead, our cost, and our crew size appended to our already existing records for all of our expeditions. Yes. So somebody pointed out in the chat, be very careful with the merge option. It will delete everything if your field is blank on the import file. They'll ended up deleting everything in a table because the fields in my sheet were blank. That is a very great caution. K. Thank you for pointing that out. So, yes, only import the columns that you are needing. Seems like that's a a common oopsie. I haven't done that yet, but now I will be hyper aware of that. Thank you. Alright, guys. We found a lot of hidden treasure today. We did found seven large pieces of treasure. Now inside of the deck that you, could download from our application, towards the end, there are some, you know, additional nuggets of information of things that you could do within your application. Maybe some things that didn't require a hands on, and just saying, hey. Guess what? You can do this. Kind of a cool thing. So, you know, maybe something like adding emojis into your applications on your forms or something like that. That's a cool little nugget that's in there. Just some examples in there. And, how are we feeling about the treasure we found today? Hi, everybody. I hope you all enjoyed the run through. So now we'll move on to the excellent part, which is q and a. So if there's any other questions, I saw a bunch in the chat that I'm actually gonna run through really quick again just for folks who might have missed them. But, otherwise, if anyone has fresh questions, now is the time. Please let them roll in. Happy to to go through them. Talk a little bit more about anything topics that folks are interested in. But I so I'm gonna start with some of the questions that came in during the session just in case folks missed it while they were watching. Someone asked back when it came to search and replace, which we covered very early on in the session, is it possible to find and replace in all records, not just the shown ones? So yes. When you use find and replace, it will work on any record in the report that you're currently looking at. So if that report is filtered, it will only change the records that are in the report. If that report is something like your list all that has every record, it will change all of them. It will run through every single one and check and change them. So you can kinda control how many records all at once you've, you wanna change just by making sure you're using the right report. Next is what if there are thousands of records and you're only the first page you you're only seeing the first page with a hundred records. Will it replace all of those records? Yes. It will keep going even if there are multiple pages. And someone asked if it does work with other field types. Yes. It does work with, well, a lot of different field types. There are a couple that I'm not remembering off the top of my head that it doesn't work with. When that is the case, it tells you that it won't work. With user fields, yes. It's gonna basically instead of giving you a free write option, it will give you sort of a menu of folks that you could find and replace with just like when you use a user field in your app. It similarly tries to help you by saying, like, these are the users that you can choose from. And then let's see. What else did we have come in? Someone was saying, could a, snapshot field be used for a, amount of time at a certain period, say, like, end of quarter, end of month? Yes. So when a snapshot field is, used, basically, what happens is you have the, snapshot based off of your relationship. When that relationship is saved, it will snag the value at that time and save it and kinda stamp it into your record. That won't change until unless you pick a different record in the relationship. So while, like, a price might change on an item that is, that's related to, that price will stay the same unless you edit it and change to a different related record, then it will stamp the new price. So that's the one caveat with snapshot fields is if you change something, you kinda lose your history. If you really need that history, what we actually recommend is, alternative is called the many to many table. You can look that up. It's a lot more complicated. I'm also happy to help folks as is the tech support team if anyone's ever curious about a many to many. They're a great way to capture multiple points of time rather than a singular point in time. They're just a they're they're a more advanced feature. So I always warn people to, like, be ready for it if you wanna jump into it. And then someone also asked a great question, which is on grid edit. They have a bunch of people using grid edit. They're a little worried about creating those, rogue records. It is not there's not a simple way to say don't allow folks to edit add records with GridEdit. GridEdit already kind of breaks a lot of the rules, the form rules, and things like that because it's supposed to be the easiest way to edit, so it's a little more free. Instead, what I recommend is if possible, make it so that adding a related record that related record field that you use is required so that folks have to put a value in there. It will stop them whenever they actually try to add it in a, credit report that's in, like, an embedded record or somewhere else and say they have to relate it to a record so you don't get orphans. The only downside would be if there was ever a reason why you'd wanna create a record without a parent. Those usually if you have a workflow that's that important, you don't want to. So adding that restriction to say you have to pick a parent, just make sure there is never a, like, a rogue record. I found that very helpful just to keep things simple. It makes people make sure they do all the steps that they're supposed to do and tells them, hey. This field is required. You need to add it. I think that was a good one. Someone asked also for table reports when you with for tape new table when you make it and it asks you to pick an icon. Yes. You always have to pick an icon. You can totally just pick the default file icon if you want. Those are just part of the navigation for Quickbase. I'm a fan of them. I use them a lot of my apps, but by all means, you're also welcome to just use the little file folders if you wanna have several apps that I'm sure are just file folder file folder. Divo can tell the difference. And then, as a reminder for everybody, all of this is available on demand. Also, when you if you look for the treasure hunt app, either through the link that I provided or if you find it in the exchange later, it includes a step by step guide in the documents table so you can go every single step one, two, three, and follow along. And then the last question I have here is when talking about grid, are there plans to recreate the capabilities to create new records and lengthen the parent records rather than creating orphan records? So the, that question yes. They're we we're always thinking about the ways to to do those kinds of things and make sure they get added correctly. Some instances they work, some instances they don't. So I always say, like, air on the side of caution. If you create records in a lot of grid instances, you can make sure you add that parent that child record if you want someone to have the freedom to do so. It's just a matter of, like, how strict you need to be about your record keeping. Or if you wanna keep that option open, but you're worried that occasionally a person might find a way to create a record without a parent, you can always build a report that is looking for just records that have a blank value in that parent record field. And it's not always great, but you can make it part of your, like, once a week, once a month workflow to double check and see, like, did anyone forget to add parents? Do I need to go back to them and say, like, hey. You missed a couple? Because as we all know, like, the quality of the data that you have in Quickbase is really dependent on the work that you do to get it in there. The better your quality of your data, the greater experience you're gonna have when it comes time to run statistical analysis, pull data from your records. I I used to work in tech support a long time ago, and there's many times working together with people. We would go through things like, hey. I wanna report on this kind of thing, but I need my data to line up. And sometimes we'd have to go back and do a little fixing. There's tons of ways to do it. Yes. There is a, training for building reports. There's a couple of great trainings in the Quickbase University. You can look in there and actually find some sessions on both report building and just general building. If if you're new to Quickbase building in general and want a really broad cross section, there's a recently created quick start session Quickbase Quickstart. They are great. They cover a bunch of everything, including creating relationships, building applications. It's essentially one hour to learning the fundamentals of building an app, and they cover the simple like, the best practices, and they'll recommend to, to other courses that are related. There's a ton of great stuff in there. There's also, for those who are interested in help in, like, topics like we covered today, there's a quickbase.com/events page. It has a ton of our previous sessions, a lot of stuff that I helped run-in the past that are technical, pipelines one zero one that gets you introduced to pipelines, feature focuses that cover previous feature releases. So there's a lot of options out there. If you're interested in getting a little bit more and you wanna sort of search what's, right for you. I would highly recommend both university and the quickbase.com events page. Yes. And so you're saying to for Chris, you had a question about, is there a way to identify records that have incorrect data? So Quickbase to let you know highlights them in red, but if there isn't a simple way to have a report that shows you all of the things that are in red, what I have often done is made a summary report that summarizes up the values in that field, and it will tell you all of the different options available. And you'll be able to see, hey. Why do I have two jewelry? And then you'll realize you have one that is incorrect. And when you click through on that summary report, it'll be a list of just all the records that have the wrong data. Then you could use the the the, find and replace just in that little mini record the little mini report and fix just those records. And, summary reports like that can be really helpful when you wanna sort through your data, make a quick summary report, pick a field that you're interested in like that, that jewelry type field, and see if anything weird comes up. Like, that's a really great way of sort of, like, I know something's wrong in my app, but I need to figure out what it is. Let me go and build a report that sort of focuses on the thing I'm most interested in. So we're about five minutes out on time. I don't wanna keep everybody for too long. If there's any other questions, feel free to jump drop them in. Otherwise, we're just about ready to wrap up. Oh, and I saw another question came in on where do I go on Quickbase for tutorials? So I would say easiest thing to do is to, either go into our events page for everything. There will be an events section on the quickbase.com website that covers both trainings and events, or if you just in Google search quickbaseuniversity or quickbase.com/university in your, window in your URL window, it is so yeah. University@quickbase.com. Yeah. Exactly. Robert just dropped it in the chat. They are both great resources for being able to, learn more about Quickbase. Alright. So I don't see any new questions coming in. Thank you so much for taking the time to join us. We really hope that you have a great experience with being a builder at Quickbase. I will make one final plug, which is if you ever find yourself doing any of these techniques and you're really having a hard time, our tech support team is also always happy to be here and help out. Or you at quickbase.com/university, you can or, community, community.quickbase.com. Sorry. I'm getting my URLs mixed up today. Community.quickbase.com. You can find our full community of awesome folks, like everybody who is helping answer questions and ask questions today. You can actually, work together to solve, ask questions, and get the opinions of other folks like you who might be doing the job like you and you just want some advice. Like, what I does this idea work? Has anyone had experience with it? Otherwise, I hope you all have a great rest of your day.