April 2026 Pipelines Qrew Meetup Recap
Hi Pipelines Qrew! Thank you all who were able to join the Pipelines Qrew meetup On Wednesday. Wes McAda shared three use cases for using Pipelines and Jinja for Project Expense Summaries. Those three include: Using Jinja + namespace to pull unique Project IDs from an expenses table and upsert parent Project records Using a callable low-code pipeline to find expenses missing a related summary, create or find the matching Project Type Summary, and relate sibling expense records Using Jinja + regex + namespace to calculate scalar dollar values, handle null expense types, and distribute records into separate Food, Lodging, and Unallocated tables Qrew tips from the meeting: Wes McAda’s Qrew tip: Think about data volume, reporting needs, and performance when deciding between relational summaries and scalar values. The best approach really depends on the use case. Jim Harrison’s Qrew tip/example: Jim brought up another potential use case to replace “search” with buckets as they can be a very efficient way to pivot and transform data in a pipeline and shared an example to the Qrew to review. Missed the meeting? Here’s the recording. Want the YAML? Reach out to me via email [email protected] for copies of it. As a reminder, we will not be hosting any virtual Qrew groups in May. Instead, we will meet up in Houston on May 18 th at 7pm on the 6 th floor of the Marriott Marquis for a special Qrew Meetup the day before Empower 2026. Hope to see you there!31Views0likes0CommentsNovember 2025 Pipelines Qrew Meetup Recap
Hi Qrew, Thanks to everyone who joined Wednesday’s Pipelines meetup. Here’s what we discussed: Dwight Munson (Sigma Technologies LTD.) walked us through two Pipeline patterns—audit logs and post-backs—that keep tracking simple and improve visibility across the org. Audit logs pipeline: Dwight replaced noisy webhooks with one metadata-driven pipeline that logs only what changed. It loops the changed fields and writes compact rows—field label/ID, old → new, modified by. He uses single vs. bulk triggers to stay efficient during mass edits. Post-backs pipeline: For Field Verification Requests (FVRs), Dwight stamps each record with the app ID, table ID, record ID, and target field IDs, then uses a single generic pipeline to aggregate locations and post totals/status back to the originating work request across multiple apps—no per-app pipelines. Qrew tips from Dwight: Always stamp origin IDs so one pipeline can post anywhere. Keep post-back targets scalar so humans can fix edge cases. Skip logging fields that only create noise—you don’t need them. Missed the meeting? Here’s the recording. Our next meetup is Tuesday, Dec 9 th at 12pm EDT — App Builders Qrew with Lee Gilmore (Primary Key Consulting) and Qrew Legend Mark Shnier on change management and app adoption with real-world examples. Thank you and have a great afternoon! Best regards,38Views0likes0CommentsSeptember 2025 Qrew Meetup Recap
Thank you to everyone who joined yesterday’s Pipelines Qrew meetup. Here’s what we discussed: Rob Mersereau, Sr. Implementation Consultant, shared an encore of his Empower 2025 talk using a Mardi Gras example to show how to integrate Quickbase with Google Calendar through Pipelines. He noted that this use case can be applied to Outlook and SharePoint. Key highlights and tips: Link to app for following along Connect & Import: Rob demonstrated linking multiple Google accounts to Pipelines to pull Mardi Gras parade events into Quickbase—one record per event. Qrew Tip: Name Quickbase fields clearly with “gcal_” prefixes so AI auto-mapping works smoothly. Push to Calendar: He showed sending Quickbase parade plans to Google Calendar, writing back event IDs and clickable links for seamless updates. Qrew Tip: Always double-check your pipeline is turned on—this is the top cause of sync issues. Keep Data Fresh: Rob recommends using Bulk Record Upsert in Quickbase to quickly update or add records and track changes. Qrew Tip: Use Google event IDs as merge fields to prevent duplicates and enable reliable two-way sync. Build Gradually: Start with simple one-way flows, then add Teams alerts, Maps API calls, or multi-way sync as your workflow grows. Missed the meetup? Here’s the recording Attached is the participant guide to follow Rob’s examples. October is EmpowerPro month! Be sure to register for EmpowerPro October 7-8. Afterward, the Qrew will host a 3-part series, EmpowerPro Product Talks, on October 22, 23, and 28. More details coming soon!68Views0likes0Comments