How to set up a child record to automatically select its parent?
Hi everyone! I've just started playing with a connected Quickbooks table. I'm trying to find a way to have the records in the Books table automatically select a parent record in my Jobs table. Each Books record has a Job Number field that should associate it with the proper Job record (each Job record has a unique Job Number), but I can't figure out how to create an automation that tells the Books record to "select the job with the matching 'Job Number' as the related Job for this record". I've tried to have it automatically write the Job Number to the Related Job field, but it just inputs some numbers and doesn't select the correct job. Any ideas? Thank you in advance! - Elena ------------------------------ Elena Larrabee ------------------------------March 2025 PDX Qrew Meetup Notes
We started the March meeting with sharing updates on development progress during the previous month. Jen went first by showing a report designed to track progress and work complete on Jobs. The use case is to provide an easily digestible view for anyone with access to the realm. The report looks really nice and provides a lot of information with links to details. The goal of the report is to replace the spreadsheets used in the past. Next Kennedy updated Notifications sent to customers around warranty information. Seeing how others use the features of Quickbase to perform work is interesting. Jim talked about a Pipeline using the Restful API to get a report from Quickbase and then again using the Restful API to UPSERT changes to the table. The Pipeline takes three steps and uses the batch method in place of loops. He also shared progress on using QuNect to UPSERT to a UNIQUE lookup on a child table. Progress came to a halt when it was discovered that QuNect doesn't allow writing to lookup fields. Prior to a recent change by Quickbase to allow mapping tables using a Unique lookup field, this would have been an error. QuNect correctly made certain the builder didn't attempt to write to a lookup field. Now that writing to a lookup is allowed, QuNect is working on a solution and should have an update next week. Elena shared her work with Fast Field forms. She is building a solution for a customer. One problem was found problem with inserting a string value to a field. There is an option on the Fast Field form builder to insert a string literal. The string isn't written to the cell correctly. The workaround is to add a hidden field to the Fast Field form to take the place of the literal and then upsert that to QB. As we discussed Fast Field we moved into a general discussion of sharing our experience with Fast Field. The general talk about Fast Field includes a brief overview of the upcoming OCR feature. We have some interesting use cases to test out and determine if the Fast Field feature is preferred to the other offerings available in the market. During the conversation, Kennedy asked about Fast Field in general as her company doesn't have access. We gave a brief overview of Fast Field and then went over the features and differences between Fast Field and Quickbase. It seems like Jen has the most production level Fast Field experience amongst the PDX Qrew. Her experience in general is the separation between the two platforms causes duplicate work during development. We all acknowledge that while this integration is only a couple years old, improvements are taking place on a regular basis. As the platforms come together we expect improvements in the integration. As the Fast Field conversation died down, we started talking about the benefits and experience of using AI. We talked about how we use AI to write some code. We also shared our requirements & best practices for using AI. The conversation then moved towards an interesting AI use case. Elena shared a code page for designing a gardening layout planner tool. The page uses the Open AI pipeline channel to fill out record data based upon how the garden is drawn by the User. The Code page is a draggable quadrant like a square celled excel spreadsheet. Users draw a garden plan into the quadrant. Then using a header with drop down lists to define plants, soil type, that are in the selected cells on the quadrant. Next the code page generates values to be inserted into a table in Quickbase. Some of the feature ideas were to include suggestions from AI about plant placement, watering, soil all based upon the plant type in the generated records. The User now has a document with facts about the components of the garden design. It's a neat idea! The problem appears when the amount of data becomes overwhelming to the AI. The code page is generating a json array to send to OpenAI and that is where it seems to not work. The problem with the example is the number of key value pairs became too large and the AI was unable to process the data easily and at a reasonable cost. Good feedback from Jacob is to use the image itself or convert the data values into a series of questions and send the questions to open AI to produce the results. The reasoning is that AI is build upon language and may be more effective/ efficient than sending chunks of data. We all were pretty excited by this observation. The meetup began to wind down and we were beginning to say goodbye when Tammie King appeared in the Teams call. Since Tammie snuck in late, she asked about the cool excel like code page. So we talked about it some more. Again, we all were pretty excited by the garden designer code page. Then we talked about hanging out at Empower and then we called the meeting to a close. Jacob recommended the Pocket Pub as he felt it was nice the last time. While at the Pocket Pub we were witness to a storm front rolling over our heads. The news forecast was for tornadoes, lightening. The weather event was windy for about ten minutes. Some of us got dust blown in our beer before we could cover them with our hands. Then it rained and we continued our conversations.08/23 Qrew Meeting
Hello All, Looking forward meeting at 3PM Wednesday. Plan for this event is to work on some projects/solutions. We will walk through ideation, planning and implementation with the goal of getting one thing done. Elena do you want to bring a laptop and one thing we can work on? If not the floor is open to requests. If there are no requests maybe we can play with the Pipelines Beta and see what we can break. As usual please RSVP if you are planning to attend so I can plan accordingly. Have a great weekend, ------------------------------ Jim Harrison transparency = knowledge + understanding : The Scrum Dudes ------------------------------Pipelines Quickbooks channel help
Hi everyone! Does anyone know how to add multiple lines to a Quickbooks invoice via a pipeline? Is that possible? For example, I have a Job record in Base that generates a Books invoice via a pipeline. The Base record has multiple child records that I need to be able to insert as multiple line items in the Books invoice. Thank you! #quickbooks #Pipelines #channels ------------------------------ Elena Larrabee ------------------------------Pipelines QuickBooks channel - invoice lines issue
Hi everyone, I have a pipeline that's been working great for about a year and just recently it's broken down and I'm having a really difficult time getting it figured out. Essentially, it's a pipeline that searches through invoices triggered by a button on my Base record - if an invoice exists it updates it, if it doesn't find one it creates one. I have it set up to search Base for several financial summary fields and insert those records as lines in the Books invoice. This has worked wonderfully for a long time, but now it just will not insert that array of records as lines when an invoice is updated (it still works when creating a new invoice). Has anyone experienced anything similar? I've tried copying the whole pipeline, I've tried deleting the "update invoice" step and recreating it, I've tried turning it off and on again, but it still just isn't working. Here it is successfully finding all 7 financial summary records: Here is the input array (with all seven objects): Here is the output array for the same step: Any help would be greatly appreciated, this is driving me crazy! I don't understand where the breakdown is between the input and output... Thank you! #Pipelines #quickbooks ------------------------------ Elena Larrabee ------------------------------Automation to create multiple records based on a multi-select text field
Hi everyone! I have a tricky question for you. I have a parent table (jobs) with a child table (schedule) with its own child table (crew assignments), which in turn has its own parent table (crew) which is just a master list of the staff. The way I have my app designed, users add schedule items in a grid edit within the main Job form. Then within each schedule item in the grid edit, there's a multi-select text field set up to assign crew members to each schedule item. It's fine, but it's just a multi-select text field that pulls crew names from the master crew table, it's not actually associating crew assignment child records with that schedule item. Having users click a report link from each schedule item and add crew assignments in grid edit mode would be adding too many steps. What I think I need is to be able to do is keep my multi-select text field, but create an automation that separates that list and then creates a child record in the crew assignments table for each name on the list. I haven't done much with list fields in automations so I'm not sure where to start. Or of course, if I'm missing something blindingly obvious about being able to create multiple grandchild records within a grandparent form let me know. Any help would be awesome! ------------------------------ Elena Larrabee ------------------------------URL button to add new record and then go to that record
Hi everyone, I feel really silly asking this, but I can't figure out how to use a URL button to add a new record and then simply go to the newly added record. This is what I have currently. And, the only reason I'm using API_AddRecord instead of API_GenAddRecordForm is because I can't get it to set field 18 to what I want, but for whatever reason it does work with AddRecord. URLRoot() & "db/" & [_DBID_CREW_TIME_RECORDS] & "?a=API_AddRecord" & "&_fid_18=" & Now() & "&apptoken=cynqae3bygzqysbuufhnqczijtxn" & "&rdr="&URLEncode(URLRoot() & "db/" & Dbid() & "?a=doredirect&z=" & Rurl()) Thank you! ------------------------------ Elena Larrabee ------------------------------October Qrew Meetup Notes
We had another successful Portland, OR Qrew meetup this month. Lee, Jen, Brianna, Ralph and myself attended. This month's meeting was a collaborative session and to that effort we had Rich Text button problems to solve. First Jen wanted to use Grid Edit in a child report on a form and have the grid edit save the edits before navigating to another page. The problem when this is done, is the parent form has no changes and therefore the Rich Text button "class='savebeforenavigating' doesn't save the changes to the child records. The solution is to add a form rule to the parent form that enters the date/time into a field onload and now there is a change. Once there is a change to the parent form, the savebeforenavigating class is called and the child records are saved. Jen was happy with the results and so we moved on to the next problem. Next Lee wanted to display images as icon/buttons from a parent table but couldn't get the image link to work properly. We resolved the problem by adjusting the syntax of the Rich Text field and then went into explaining some of the syntax of Quickbase formula language and how it is separated from Rich Text HTML. We had solved two problems and it was getting close to the 2 hour mark so we called an end to this months meeting. Afterwards we headed over to Izakaya Kichinto for some snacks and a drink or two. Next month we are looking for a presentation. Lee mentioned AI and I think there may be some interest in learning more about how it can be used with Quickbase. Thank you again to everyone for attending. The meeting was successful as we worked together to learn and solve problems, which is always fun. ------------------------------ Jim Harrison transparency = knowledge + understanding : The Scrum Dudes ------------------------------
Pinned Discussions
Group Content
About Portland (OR) Qrew
Come meet up with members of the Portland, Oregon Qrew here!Owned by: LeeGilmore, LeeGilmore1, and JimHarrisonCreated: 2 years ago
Open Group