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.April 2025 Qrew Meetup Event
Portland Qrew is meeting the forth Wednesday at 3PM PST at Harder Mechanical Contractors and also on Teams. We'll talk about Empower a little more, key takeaways, plus deltas and other interesting gossip. Then we will talk about current projects, new changes and challenges. Anyone can show off work and cheer each other on to higher heights. We ask attendees to bring problems to solve and then work together to provide a solution. Anyone willing to share is welcome to have a problem solved by a team of very nice people who all love helping. Afterwards I suspect we will go out somewhere and welcome recommendations. If you would like to join remotely email jharrison@harder.com directly and he will send you a Teams invitation.February PDX Qrew Meeting Notes
Diego Alvarez, Tammy King, Pat Wenger, Pierce Wagner, Nico Cantillo, Lee Gilmore, Jonathan Miller, Elena Larabee Intros Diego Alvarez was the first to present a problem. He is working on a formula to compare date values between a set of fields. The difference between dates determines a duration between start and finish and is displayed as a number of days. The collaboration energy was strong with this one as we all discussed and postulated the best solution. Tammi really took the lead with assistance from Pat, Lee and Elena. In a few minutes we had a working formula and we were ready to move on to the next problem. Pat and team Harder have been working on understanding best practices and methods of improving Dashboard report loading performance. We have many Dashboards containing gauge reports that are struggling to load. Some reports we call My Reports, filter by the current user. My reports allow each user a custom experience. Quickbase tells us the username lookup is likely the cause of the problem with slow load times. As a group at Harder we have discussed this many times but are still unclear on the logic behind the recommendations of using the email address over the QB Username. Quickbase recommends using the email address with a ToUser() formula versus using the QB Username. At the Qrew meetup, no one had a solid explanation and we weren't certain how to explain why one works better than the other (this is going to be my Elephants Child at Empower this year). One response from Lee was to use a User table, which is pretty much what we have with our Employees table. We use both User type fields and an Employees table in various locations throughout the realm. The easiest way to set up a nice gauge report is to use the User field, employing an Employee table is more complex and takes longer. Another solution is to use a Formula check box to identify where a User field in the record is assigned to the current user. In this case we use the formula UserToEmail(User()) to inform a check box. Then in the My reports filter we look for is equal to in place of is current user. The same filter is applied to the Gauge report as well. The explanation is that the formula does all the work once, whereas the is current user performs the same work for each report. I would really like to see a visual representation of how this works. Next Jonathan was asking for Kennedy. Kennedy wants to know how to transfer a pipeline from one account to another. There are many variables involved in answering this question. But here is a tldr general answer below and we can work on this at the next PDX Qrew meetup. If the email address is owned by your company, then to transfer Pipelines over to another account, as a Realm Admin, change that email to a service account. If the email is not on your domain, log on to that Users pipelines and transfer them manually. Below is how to transfer manually in several steps. First export the YAML. Next setup a service account. Last replace the slugs and import the YAML to the service account. The goal is to replace this part of the YAML called a slug: iAmasLuG and then import the modified YAML to the desired account, preferably a service account. # Account slugs: # - quickbase[iAmAsLuG]: Click "Profile and preferences" located in the upper right corner of the dark grey App bar Select Impersonate a user and enter the user to impersonate (the transferring away from account) One at a time, click the pipeline to export Click the kabab icon Click export Click "Download all YAML" or select all the text inside the black background in the Export Pipeline window and save it to a text file Once all the YAML is downloaded, open the YAML in VS Code or Notepad++ Find the all the slugs in the text and replace with the one from the service account What service account? Read on. Create an alias User: Have IT add a publicly accessible email address to your domain as an alias forwarding to one or more Users who will access the Pipelines Verify the email can receive email from outside the domain by sending an email to the address from gmail or some other email service. If you get a bounce email, tell IT to make it public Add the email as a User to Quickbase On the Users page of the admin console, locate the email Under authentication select Use Quick Base to manage password ~ wait for the email The registration email is sent to the alias email and then forwarded to you Click the register link and fill out the form with information. Record the information in a secure location like Roboforms so others can access this information in case you win the lottery Make the alias email into a service account: Admin console > Permissions, add the User to Permitted Users and groups with Build Pipelines and Create user tokens toggled on Admin console > Users, search for the Alias User, click on the User so the sidebar pops out In the sidebar scroll down and toggle on "Use as a service account", add whoever needs access to the service account Refresh the page and look at Profile and preferences dark grey upper right, there should be a Switch Accounts section and the alias is listed in that section. At this point you have all the Pipelines YAML now you need a slug. Get a service account slug: On your account click Profile and preferences, click switch to service account Once connected as the service account, click Profile and preferences again Click Channel accounts On the channel accounts page copy the Account slug to Quickbase connector Open each of the Pipelines and find and replace the old slug with the service account slug On the service account import the modified slug YAML files Test the import Turn off the old Pipelines Turn on the new Pipelines Switch back to your account Easy right? To be fair, once the process is understood, it is really easy to perform and can be done in a few hours depending on the number of pipelines to move. Also this process is only going to happen once because from this point forward everyone is using the service account and no one is adding Pipelines on their account. @Kennedy, join us for the next Qrew meetup and we can walk through the process. Next Elena shared some interesting methods around using the Quickbase Document Generation (doc gen) "Document templates" tool. She talked about solving the problem of combining individual PDFs into one pdf output (we call it bundling at HMC). The process is done using the Document Generator Restful API. A JavaScript code page is written where one generates PDFs on multiple child records via URL parameters. Then sends the separate PDFs to a PDF microservice like Convert API. Convert API loops through the PDFs and combines them into a single document. The final document is put back in a record in the App as an attachment. For Elena's solution the use of Chat GPT helped complete the JavaScript process. Elena is using PDF Lib to perform the bundling. The only caveat to this solution is file size. If the combined file size is greater than the allowed file size (50MB last check), this method does not work. Informing the User who clicked the button of the error is the next problem looking for a solution. In regards to security and uploading business files to microservices, it is not certain who has access to the files uploaded, further investigation is recommended. Nico also has customers who are using the Document Template feature in Quickbase. He mentions the cell height is limited to 50px statically and cannot be changed (without effort). He was unable to explain why 50px is the defined setting and was equally confused. Maybe someone at Quickbase can explain the 50px baseline and why this value was not given to the builder to decide. Finally we discussed a Pipeline question relating to whether it is better to batch update or loop update records on a scheduled pipeline. For this problem I have a garbage collection process where I want to schedule the clearing of values entered in different fields after a condition is met. In this case, we have employee records where one or more Employee's are Onboarding and upcoming dates are filled out prior to Onboarding date as a mean to prepare. The Pipeline looks for records two weeks after the onboarding date and clears the date fields. In my experience with Integration Reads, it is more efficient to batch update over loop update. I started a Pipeline using Resful API to get a report. Once I had the report I wanted to parse the JSON in the report to prepare a csv for upsert with blank values. The entire group suggested this method was easily done with a formula field and a search and loop update records Pipeline. I still would like to see if it is possible to get a report, make some changes and then batch upsert at some point in playing with Pipelines. Overall the meeting went really well and it feels like we solved some problems. Afterwards we decided to visit Eem and continued our conversation around Quickbase life the Universe and everything.March 2025 Qrew Meetup Event
Portland Qrew is meeting the forth Wednesday at 3PM PST at Harder Mechanical Contractors and also on Teams. We'll talk about Empower a little and maybe make some plans for the event. Then we will talk about current projects, new changes and challenges. Sometimes we show off our work and cheer each other on to higher heights. We ask attendees to bring problems to solve and then work together to provide a solution. Anyone willing to share is welcome to have a problem solved by a team of very nice people who all love helping. Afterwards I suspect we will go out somewhere and welcome recommendations. If you would like to join remotely email jharrison@harder.com directly and he will send you a Teams invitation.January 2025 Meetup Notes
Attendees: Kennedy Maxey, Esther LaVielle, Nico Cantillo, Jen Clark, Daniel Jeon a Denver Quickbase builder 12-14 years, Elena Larabee & Jim Harrison We held the January Monthly Qrew meetup a week early as planned last month. Next month we go back to the regular fourth Wednesday schedule. The meeting started with Introductions. A new attendee Daniel Jeon joined us remotely from Denver, CO. Daniel has several years of experience with Quickbase. We are excited to hear what insights he has to share. Everyone had a chance to say hello to Daniel and give a brief introduction as well. Once the introductions were complete we moved on to asking if there were collaboration questions from the group. Collaboration: Jen asked about anyone's experience with setting up Single Sign On using Microsoft Active Directory. The example showed her login process takes three clicks and doesn't keep the login active once the browser is closed. Several commented there are some settings in the Admin console and Quickbase Support may have to make some changes on their end as well. She is planning to contact Quickbase Support. Nico Showed an App he built this past month around the management of stringing tennis rackets. The design is to keep track of materials, cost and time spent on each racket. During the presentation Kennedy asked about the Document Template. Nico explained how he is using Document Template to print forms. Kennedy looked and doesn't have access to the Document Template since her Realm is not on the plan that offers the Document Template feature. We suggested either a Builder Account, make a test, show it off and see if there is budget or Nico is going to see if Quickbase can turn it on so she can test it out. Daniel asked about Webhooks. He wanted to know if they are "really" going away. Nico responded that yes Webhooks are going away as Quickbase wants traffic going through Pipelines and not Webhooks. I pointed out that Webhooks are going away from the UI and moving forward will be managed via API. There is still a lot of work to be done before Pipelines is ready to replace Webhooks. We then talked about Zapier, Workato and Pipelines. Daniel has experience using Zapier and I asked about the experience since we use mainly Workato. He said the UI/UX is more feature dense than Pipelines, there is a Dev and Production environment for example. Next Jen asked about ideas for building a tool management system. The idea in essence is Users fill a shopping cart with Tools and then check them out. As the checkout process happens quantities are updated in an inventory table. Elena has the most experience with inventory management and building tools in Quickbase. She mentioned using a Code page. We talked about using code pages and Quickbase API to get records from a Query and then add the template new records to another table as well as update the quantity values. This is all possible with a firm understanding of JavaScript. Pipelines is also an option but doesn't provide a live real time experience for the Users. We talked more about Code pages, service accounts and performance tools. The last question came from Jen regarding a new Pipeline process. The idea is getting the most recent files from a SharePoint folder. We looked at several examples of the file structure and the recommendation came up to use Bucket. I have an example I can share but it has been a while so we decided to hold off and look at it again at the next meeting Jen is available. We arrived at the end of our meeting and said our fair wells until next time.February 2025 Qrew Meetup Event
Portland Qrew is meeting the forth Wednesday at 3PM PST at Harder Mechanical Contractors and also on Teams. The plan is to talk about current projects, new changes and challenges. Sometimes we show off our work and cheer each other on to higher heights. We ask attendees to bring problems to solve and then work together to provide a solution. Anyone willing to share is welcome to have a problem solved by a team of very nice people who all love helping. Afterwards I suspect we will go out somewhere and welcome recommendations. If you would like to join remotely email jharrison@harder.com directly and he will send you a Teams invitation.Qrew December 2024 Meeting Notes
We started the meeting giving our general status on what accomplishments we made this month. I would say the overall theme this month was everyone was busy. Due to being busy, not a lot of Quickbase work was done. We started off giving general updates with Dorian. Dorian spent some time this last month learning more about Quickbase. He is taking online QB Training and setting up a builder account. It will be exciting to watch Dorian progress through the learning process. Next we heard from Kennedy. Kennedy has been showing the Quickbase feature set off to other Big Sky stakeholders. One of the best ways to build interest in what Quickbase can do is showing it to others. When showing it to others, they start asking if it can do this or that and that builds on the development process. These simple questions may seem daunting but write them down anyways. Our brains process information at different rates. Sometimes it takes a while to think of a solution. Next thing you know, you're building and supporting an entire infrastructure the business relies upon to get work done. Next Diego talked about his experiences this month and had some really interesting questions for the group. Diego is getting comfortable conceiving and building structured systems. He shared observations on Users asking for changes and having to re-design a structure that is already in place. Another observation is finding what is already built and hasn't been used. Finally there is what needs to be added and how to do it in a way that gets used and still performs. Jen talked about building out some Apps for the service department and some UI improvements. She did a lot of building this month. She also has been working on integrations with Power Automate and HTTP connectors in Pipelines. Lee Gilmore made some comments regarding New forms versus Old forms. Learning what works for the old form versus the new form UI/UX and becoming familiar with the changes. We all agreed there is no reason to move to new style forms until Quickbase provides the same feature set as the old style forms. This feature set includes mobile functionality and form edit mode grid edit with sub-form rules. Sadly this leaves User experience in this strange state of unfinished partial solutions. Quickbase no doubt wants to proclaim new forms done and deprecate the old style, but doesn't seem interested in pushing New Style forms over the done line. Hopefully next year we will see some improvements to user experience. Elena spent time last month learning about Marketo. Also her team is working towards building a common data model for the Construction Apps in the Exchange. She shared her experiences learning about the complexity of designing the distributed data model with scalability in mind. The development of the Apps in the Exchange is complicated by answering questions like "how complex do you built it" and still have it be flexible enough to meet general requirements. At this point in the meeting, Diego asked Elena a question regarding overall decision making for product development. The question triggered an interesting conversation where nearly everyone had something to say. The question he asked; Who are you talking with to determine what solution to build and how deep you need to go? Diego then asked about how to communicate with stakeholders who aren't really interested or don't give feedback . Lee said treat the communication or lack thereof like an intake form. As builders we want to help and provide a solution. The problem happens when we get lost in the solution and are unable to provide what they are asking. It is important, and challenging, to listen to others commenting on our work and focus on their words, not a solution. Sometimes people are asking or saying things because it is how they process whatever it is we are showing them we built. There doesn't always have to be a solution. After that we went on to talk about other experiences we have working with others. Meeting with people and listening to their ideas. One interesting observation is people don't have a full sense of control over data in Quickbase. Having confidence in the data is important to getting and keeping User interest. It is easy to identify the lack of confidence when Users want to download the data and process it themselves in Excel. The challenge as a builder is to design User confidence in the data. We continued talking about how to structure data. Planning and best practices. Next Jim talked about progress on building a new Subcontractor form and process named Subcontractor Prequalification. The idea allows a User to formally request a Subcontractor is added to our Work Order system. The process replaces the current system, which is based around email, Teams and phone calls. The goal with the Subcontractor Prequalification process is to locate the information in a single database with progress alerts. Users can choose to receive Notifications on status changes, ask for status updates, stop getting notifications or learn when the Subcontractor is or isn't added to the system and why not. A benefit to this process is we now have a datastore of previous requests anyone can review before putting in a duplicate request. There were no collaboration questions this month for Quickbase development but it felt like we came together discussing Users and right sizing app building in general. Overall it was an interesting conversation, covering a problem that is complex and challenging. Any professional builder has had to deal with questions that have nothing to do with building the software part of applications. How much satisfaction does the builder provide the User versus calling it done? Afterwards we went to Broadway Grill & Brewery and continued the conversation eventually leading in to tales of upcoming and past travel. We decided then the PDX Qrew meetup next month will also be a week early and then fall back to the fourth Wednesday in February.January 15th PDX Qrew Meetup
Portland Qrew is meeting a week early again for the dark months. The plan is to talk about current projects, new changes and challenges. Sometimes we show off our work and cheer each other on to higher heights. We ask attendees to bring problems to solve and then work together to provide a solution. Anyone willing to share is welcome to have a problem solved by a team of very nice people who all love helping. Afterwards I suspect we will go out somewhere and welcome recommendations. If you would like to join remotely email jharrison@harder.com directly and he will send you a Teams invitation. We do not record or AI these meetings.November 2024 PDX Qrew Notes
Attendees: Dorian Gibson GSM - Jen Clark GSM - Lee Gilmore QB - Jonathan Miller QB - Elena Larabee QB - Nico Cantillo QB - exec cust success Esther LaVielle QB - QB Kennedy Maxey Big Sky Montana, joined last year, subs, project management Tammie King - work tracking apps, client transfers Pierce Wagner HMC - Jim Harrison HMC - Diego Alvarez HMC - Big Qrew this month! Many attendees from Quickbase came to the event to see Johnathan Miller. Unfortunately Jonathan was held back by the storms of fall in the PNW. To give some scale to the events, there were hurrican force winds at the coast and we made the news-drama! Better luck next time Johnathan. Luckily we have Teams and got to see Jonathan safe at home. We started the meetup with introductions and an opportunity to talk about ourselves, where we work and what we do. After introductions we asked if there were any collaborative or problem solving questions from the Qrew. Tammie K said she had some questions about time, as in what is Quickbase time and how to handle it in Notifications expected to send during local time programmatically. Good Question Tammi! The time problem is in the Photo Shoot Scoop App. The App is a scheduling tool with reminder Notifications. The App uses EOTI for Customer access and an Internal App for photoshoot process management or scheduling. One feature sends a reminder email to the photographer the night before the photo shoot. The uncertainty appears when asking how to calculate the correct time to send the email in Pipelines. The uncertainty continues on what happens to the email time when daylight savings time changes. These are very good questions Quickbase could spend a help page explaining expected behavior of time and how to manage the problem globally and locally. The current solution is to press the button a day before the shoot at the right time. Lee Gilmore had and idea and some information at the ready. Lee said time setup is available in the new custom email feature allowing specifying a send time. The details to the time setting is it is in UTC. We were not certain how to handle time zones and changes due to Standard or Daylight savings. Also several attendees mentioned that Pipelines time is UTC and Builders really want to use a formula to determine local time. I would love to see an article in the QB Help that investigates the detailed scenarios for this time problem. Time is not easy to solve, it is generally easier to use UTC globally and then make corrections at the local instance. Next we had a new Qrew join the event from Montana. Kennedy M says they are rolling out a database. The database is designed to handle warranty tracking for real estate properties, job locations and current or upcoming projects. The system uses EOTI for customer login. We are looking forward to hearing more from Kennedy in the coming months. Another new PDX Qrew name, Dorian G also attended remotely. This month the introduction and update is they are maintaining current processes and getting comfortable with QB. It takes about a year to get comfortable with Quickbase and we look forward to being a part of the experience. This month Jen C is working on variances in inventory, how to manage inventory, working with a Customer (co-worker). Service App on FF. Diego A is currently working on Pipelines and running into an error. The Pipeline step to search a table is confusing in that the next step pretty much requires a loop through the results. Since Pipelines allows Builders to Search Quickbase and not add a loop it is easy to get into a state where the process fails. I suspect it is part of learning how to low-code ones way into a solution. Learning Pipelines is next level in Quickbase and takes time. It's good that Elena was able to provide an answer and Diego is back on the way to completing the Pipeline. Pierce W says this past month has mostly been working in Workato. Jim H gave an update on a SQL process. We have a Training Library and genreate Training records for Quickbase Users based upon their Job description, it's complex and was written using variables and a WHILE loop. The old method was very slow and limited in scale. The new method takes advantge of Uniqueification and UPSERT methods recently released by Quickbase and it is awesome! In other processes that once took thousands of Integration Reads and minutes to complete, we can UPSERT an entire dataset and instantly update or add records all based upon the unique field and not the record id. Next Elena mentioned the kanban overlay is working. We got a demo and the page is looking very professional. Code pages are really an end game for the low-code builder, releasing them from constraints built into the Quickbase UI. In Elena's example a dashboard with an iframe loads a code page designed as a Kanban report replacement. The features setting the Code page apart from native Quickbase Kanban are impressive and really should be how Quickbase offers these solutions. The nice thing is Quickbase offers a solution for the Builder to make it all work all based upon gumption. Another attendee Jonathan M gave an update on the roof and an introduction. Jonathan is now the PNW Quickbase rep, congratulations! This month was spent planning for this new position, Qrew meetups and learning about tire chains. We are happy to hear the roof is good. Nico C just came back from a Customer Qrew Okto engagement. The event focused on using Document Creation & Secure Links to provide a solution for a Contract life cycle form. Nico was really excited about the solution and wanted to give a presentation. The soultion uses Secure Links to EOTI in this case a Vendor. The Vendor opens a form, fills out the form and submits it back to the Owner. The Owner receives the form, does some work and then sends a printed document to the Vendor. The solution also allows for setting end dates to expire the link, meaning if EOTI gets a hold of the link it may not work. Esther L gave an update on scheduling all the Qrew meetups for December. Next goal is getting more presenters at the events. Lee G gave an update on the Thanksgiving planning app. Everyone agreed Marshmallows do not belong in Macaroni & Cheese. Last thing I recall discussing is the announcement of Empower 2025. Empower is taking place in New Orleans. Event dates are March 31 & April 1st. Some mention was made that Ben Simon is planning something with Beignets, we look forward to enjoying some Beignets with Ben. We went to the Pocket Pub, Lee likes it and the Jalapeno Poppers are very nice.December 18th PDX Qrew Meetup
Portland Qrew is meeting a week early again for the dark months. The plan is to talk about current projects, new changes and challenges. Sometimes we show off our work and cheer each other on to higher heights. We ask attendees to bring problems to solve and then work together to provide a solution. Anyone willing to share is welcome to have a problem solved by a team of very nice people who all love helping. Afterwards I suspect we will go out somewhere. I am thinking Eem but welcome other recommendations. If you would like to join remotely email jharrison@harder.com directly and he will send you a Teams invitation. We do not record or AI these meetings.
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