ContributionsMost RecentMost LikesSolutionsRe: Displaying most recent and next upcoming recordHi Laura, Thanks so much for taking the time to test this out, and for helping me think this through. After a good night's sleep, I realized that you're right, of course: I need to connect the cases to the training advice, which is the crucial thing. After thinking about this, I think that the complication of connecting them is ultimately not worth the slight increase in convenience. So I'm sorry for wasting your time, but I appreciate that you helped me figure out why it's not worth it! LauraRe: Displaying most recent and next upcoming recordThanks so much, Laura! I like your idea to simplify, but I think your way would rely on cases always being entered chronologically in terms of when they happened, and therefore Record IDs always being in order from smallest (earliest date) to largest (latest date). Unfortunately, we can't rely on that -- we sometimes find out about cases months after they happened, which is why I built it on Date rather than Record ID#. I'm not seeing how your summary field for the first case after receiving advice is different from mine, other than being based on Record ID#. For some reason, summarizing by the minimum [Date of Case] when [Date of Case] is after the date in the field [Date of Teaching Advice] is not working. I did not know about the new Summary Combined Text Field! That's very interesting, and could be really helpful. I'll play around with it and see how I can use it. Thanks again!Displaying most recent and next upcoming recordHello! My app is used to track my team's relationships with teachers, who use our cases as teaching material in their classrooms. My team is interested in seeing how a teacher's experience using cases changes once we offer them teaching advice.For this reason, it would be helpful to be able to see information for the teacher's most recent case before we offered advice, as well as for the next case that they taught. My two relevant tables areCases and Teaching Advice. 1 Teaching Advice has many Cases. I am halfway there. I've successfully figured out how to pull in information for the teacher's most recent case: 1. Summarize the Maximum Case date where the [Case date] is before the date in the field [Teaching Advice Date]. Call this [Most recent case before teaching advice] 2. Look that up down to Cases. 3. Summarize the maximum [Record ID#] where the [Case date] is equal to the date in the field [Most recent case before teaching advice]. Call this [Record ID# of most recent case before teaching advice] 4. Then I created a reverse relationship where 1 Case has many Teaching Advice, based on the reference [Record ID# of most recent case before teaching advice], which summarizes the maximum of Record ID# based on [Case date] is equal to the date in the field [Most recent case before teaching advice]. I added the relevant lookup fields I wanted to see. Then I attempted to duplicate all of these fields, to pull in information for the teacher's following case, with a couple of small changes in italics: 5. Summarize the Minimum Case date where the [Case date] is afterthe date in the field [Teaching Advice Date]. Call this [Case immediately following teaching advice] 6. Look that up down to Cases. 7. Summarize the minimum[Record ID#] where the [Case date] is equal to the date in the field [Case immediately following teaching advice]. Call this [Record ID# of case immediately following teaching advice] 8. Create another reverse relationship where1 Case has many Teaching Advice, based on the reference [Record ID# of case immediately following teaching advice], which summarizes the maximum of Record ID# based on [Case date] is equal to the date in the field [Case immediately following teaching advice]. I am running into a problem with step 5, and I can't figure out why. The field won't populate with information. If I change "after" to "before", then the information does fill in, but it's the wrong information -- it's all of the information for the most recent case, not the following case (which makes sense). This makes me think that either I have one small mistake that I'm not seeing, or that Quick Base won't let me do multiple relationships between the same two tables. I'd appreciate your advice! Thank you! ------------------------------ Laura ------------------------------ Re: Importing Excel file to multi-line text field -- Quick Base adds ""_x000D_You're right, I've been importing from an .xlsx file, but I just tested a CSV file and that fixes the problem. Thank you!!Re: Importing Excel file to multi-line text field -- Quick Base adds ""_x000D_I'm importing from a file.Re: Importing Excel file to multi-line text field -- Quick Base adds ""_x000D_Thank you! It looks like both of these options will just remove the line breaks, but I want to preserve them, because the text will be more readable in Quick Base. Do you know if there's a way to preserve the line breaks without getting "_x000D_" added?Re: Importing Excel file to multi-line text field -- Quick Base adds ""_x000D_Thanks, Justin! Removing the carriage returns makes sense, but can you please elaborate on how to replace them with newlines?Importing Excel file to multi-line text field -- Quick Base adds ""_x000D_Each week, I import data from an Excel sheet into one of my Quick Base tables. One of the fields is a multi-line text field. In the process of importing, Quick Base adds "_x000D_" wherever there was a line break in the Excel cell. For example: This is how my data looks in Excel: "This is an example of the comment I'd like to upload. Sometimes there are multiple lines in the comment." This is how it ends up in Quick Base: "This is an example of the comment I'd like to upload._x000D_ _x000D_ Sometimes there are multiple linesin the comment." I like that the line breaks are preserved, but it's a pain to grid-edit after my import and manually delete "_x000D_" wherever it appears. Does anyone know how to prevent this from happening? Thank you!Re: Searching by a specific field within a reportOkay. I didn't know about the <ask the user> filter, which isn't exactly what I was looking for, but I think it's close enough to serve my needs. Thank you very much for your time and for telling me about it!Re: Searching by a specific field within a reportYes, I think we're talking about two different magnifying glasses. I originally thought you meant this one, which displays within a specific report: But now I think you are talking about this one, in the upper right corner: But if I click on the upper right corner, it takes me out of my report and searches my entire table for a specific field. I'd like to search within my report. It feels like I should be able to do a more specific search within the search box in the first of my two screenshots. Going back to my original example, it feels like I should be able to search something like "{Teacher Name}=John Smith" ("Teacher Name" being the field name) rather than just "John Smith." Is there any way to do a more advanced search within a report? Thank you!