Using QuickBase for Surveys
Surveys in QuickBase Part of the charm of QuickBase is that the platform can be used for many different purposes – there are all kinds of use cases already at work on the platform, but also every day new ones are being thought of to be implemented. One of the more popular ones is conducting surveys. Customers will need an easy way to gather survey-related data from either their customers or partners or others, and will need to report on this information to see how they are doing. Setting up an application to do this is relatively straightforward and reports can be easily created to display insights either in tabular or graphic format. The first thing you will need to do is create a table for storing the results. This is the easiest part. You may want to link this table to a customers table or elsewhere, but for now, let's keep the table on it's own. Next, grab your survey and take a look at the questions that make up your survey. Some will be questions that require a user to place a rating as a response, while others may be to select from a multiple choice type field. List out your questions in a document or spreadsheet, and then identify what types of fields they will be. Some will be ratings, others multiple-choice, while others may be open area text answers that will require some extra space. You'll probably want to save the date these survey results were added too. What may or may not be needed is the identification of the respondent. If it's possible that the responder will be a QuickBase user, then a user field will be needed. After listing out these questions and their field types, start by creating the fields in the table you have started. Don't worry about the order you enter them in, as you can reorder these on the form in a minute. Once you have the fields created, click on the "New ___" green button so that you can view your form, this is where the survey will come to life in a few minutes. Using the document where the questions and fields are listed, go through and right-click on each field in order to access the form's properties – you want to customize the form here, the fourth option in the menu list ("Edit the properties of this form element"). For each form element, you will simply click on the "Use Alternate Label Text" checkbox and type in what your survey question is for that field, where the answer or response, will go. Take time to get used to this editing process, and reorder your survey questions appropriately. You may want to also create formula fields that summarize respondent replies, so try to name your fields in a manner that makes sense to you, the administrator. You'll use these field names in formulas and reports, so it helps to keep them simple and straightforward. For further information on surveys, please take a look in our application exchange for several excellent examples! ------------------------------ Sean Padian ------------------------------51Views0likes0CommentsDynamic Form Rules Showing Section/fields - works on form edit but not on form view
Hey QB community! I'm working on my project management tool this morning and try to make a conditional rule for my tasks to show a few fields when the task is assigned to a specific department called communications. the problem is the rule works well when I click into edit the task. Once I fill in those fields and hit save to fields don't show in the "view" form when the task is saved and assigned to communications. I don't have the pink error message I have the fields set-up to show on Edit, Add, or View. Please help me update this form as I want my users to be able to see these fields when simply viewing the task. Peace & Love ------------------------------ Jack Woods ------------------------------35Views0likes8CommentsBar Code Uses
Hello all! I found a useful app in the Exchange for making and reading QR and barcodes at App Detail (quickbase.com). I'm trying to use this for our calibrated tools inventory. We have a unique identifier for each tool. I'm able to use the rich text formula function to create a bar code or QR code for each of the tools. What I'm not sure of is how to put that into use. I want to be able to scan the code and then check the tool out (either for use or for calibration and testing), and then check it back in (either after use or to document its calibration). Does anyone have an example of something of that nature that I can try to implement? Thank you! Mike ------------------------------ Mike michael.rorstad@ameebay.com ------------------------------35Views0likes5CommentsReal Estate Problem: Multiple agents per transaction and commission splits (help me!!)
Hi all! First time poster here. I have been working on this problem for a few days now, plus religiously combing through all these wonderful discussion posts; but still can't find my answer. Here's my problem: I work for a real estate company and am tasked with designing our database. Right now I have two tables, one is Transactions and the other is Agents. Every transaction has at least one agent, but sometimes it has two. I want to be able to assign each transaction to two different agents, so that when I pull an agent, it will show each transaction they were involved with. Each agent has a different split commission percentage. This means the total from the transaction is split differently for each agent in the transaction. I only want the split commission to be linked to each respective agent. So if Agent 1 is Jane Doe and Agent 2 is John Deer, I don't want Jane's commission to be linked to John and vice versa. I got through the first step, but the second one really stumped me. I set up reference fields for each agent and while it would allow me to select two different agents in the ref fields, it wouldn't let me split up the fields per agent. I built a pipeline for it but it didn't work (because I kinda suck at pipelines lol). Please please help, any advice is welcomed. Thank you so much in advance! ------------------------------ Karah W. ------------------------------13Views0likes1CommentCreating a Discussion board
I am working on creating a discussion board and struggling with connecting records. I was able to create a discussion board based on the sample on in QuickBase Builder, but cannot get the thread ID to populate and connect. Is there a class that will take me through start to finish on how to create a discussion board? ------------------------------ Lynda Schutter ------------------------------13Views0likes2CommentsCreating Revision form in quickbase
Dear Quickbase Solver, I have a problem that i need to solve in my organization. We have form Purchase that already establish and i need to make a revision purchase form in it. For example, Purchase form is already submitted and approved and suddenly the requester want to change the items inside the form. Easy way to do this is requester just edit the items and click save, however we would like to record the previous form approved as a history record for us to view. I hope my question is clear enough to understand. How can i execute this function in Quickbase ? Many thanks ------------------------------ Quickbase Admin ------------------------------12Views0likes2CommentsNovice QBaser...
I'm struggling with building out a CRM with minimal tables. I have three tables...Company, Contact, Opportunity. Company has a one-to-many relationship with both Contact and Opportunity. Contact has a one-to many relationship with Opportunity. With each Opportunity, there are multiple stakeholders. I'd like to add those stakeholders to the Opportunity record and in some cases it might be two and in other cases it might be five. I cannot figure out a way to add multiple contacts to the Opportunity. I don't know if it complicates it or not, but some of the contacts might be connect to different companies. Here's a rough illustration: OPPTY NAME: Acme Mfg VALUE: $32,000 EXP CLOSE: May 2021 ACCT MGR: Bob Smith SOLUTIONS: 20 hrs consulting, 40 hrs development, 8 hrs training, compliance reporting STAKEHOLDERS ============================================================== contact company status phone email -------------------------------------------------------------------------------------------- John Doe ABC Consulting partner 205-221-2210 jdoe@abc.com Jane Doe Acme client 205-444-1310 jadoe@acme.com Bill Smith Acme client 205-444-1311 bsmith@acme.com Joe Smith Acme client 205-441-1312 jsmith@acme.com Ken Hamm Deloitte partner 800-877-1200 khamm@deloitte.com Is this doable in QuickBase? Without adding multiple "Contact" tables? I just want to pull multiple contacts from multiple companies into a list associated with each opportunity. I want to keep all companies and contacts in a single place. ------------------------------ Michael Murphree ------------------------------11Views0likes1CommentCombine URL buttons' api cals
Hi community, I am building an ERP system and I need some help about combining api calls in one URL button. As shown in the below screenshot, there are status notes and documents tabs in an opportunity record. Also, at the bottom you can see a button of Convert to Sales Order, which can take a bunch of information from an opportunity to a sales order. But it cannot take related status notes and documents to the other table. I would love to have, when I click on the Convert to Sales Order button, the related status notes and documents from the opportunity record will also be brought over to the new sales order record. Please be mindful that, opportunities, sales orders, status notes and documents are four different tables. The relationship: one opportunity to many sales orders; one opportunity record to many status notes; one opportunity record to many documents; one sales order record to many status notes; one sales order record to many documents. URL for the Convert to Sales Order button: URLRoot() & "db/" & [_DBID_SALES] & "?a=API_GenAddRecordForm&_fid_22=" & URLEncode ([Record ID#])& "&_fid_20=" & URLEncode ([Related Customer])& "&_fid_24=" & URLEncode ([Sales Representative]) URL to add document in the Opportunities table: URLRoot() & "db/" & [_DBID_DOCUMENTS] & "?a=API_GenAddRecordForm&_fid_13=" & URLEncode ([Record ID#])& "&z=" & Rurl() URL to add document in the Sales Orders table: URLRoot() & "db/" & [_DBID_DOCUMENTS] & "?a=API_GenAddRecordForm&_fid_11=" & URLEncode ([Record ID#])& "&_fid_12=" & URLEncode ([Related Customer])& "&z=" & Rurl() ------------------------------ Thank you for your help! Davy Ou, Quantitative Financial analyst Certified QuickBase Developer, Lifetime learner https://www.linkedin.com/in/davyou/ ------------------------------9Views0likes0CommentsData Modeling
Data Modeling So, what exactly is data modeling? Well, it's simply a way to structure and organize your data. It provides you with a structural foundation in graphical form that you can use as you build out your application correctly - the first time. Data modeling provides the structural foundation - in graphical form - of what you're going to build in QuickBase. There are three (3) types of data models: Conceptual Logical Physical Conceptual models aim to provide context as to the business understanding of data, not a technical one. These are used to facilitate a discussion among businesspeople about their systems, processes, and organizations. Logical data models describe entities and attributes and the relationships that bind them. While the physical models then implement the logical model as tables, fields, field types and relationships. We are going to focus on the physical model, as it relates to QuickBase, implementing the logical model as tables, fields, field types and relationships in a QuickBase application. The #1 value is identifying which entities are your tables, and how are they related. This tremendously helps builders who are new to our platform, when building their first apps. Let's get started… So, where do we start? How do we make sense of our data? The first step is to write down, to articulate, what it is that you are attempting to do. Using plain language, simply state what the business problem is that you are trying to solve, and what a desired solution may involve. There is no need to get overly detailed at this point in the process, but you will want to make sure that you clearly state what it is that you are setting out to do. Then, begin by simply observing the language that was used to describe the business problem we are attempting to solve. By looking for the nouns – the people, places or things – that used. By observing the words used in your description, you will begin to see patterns or trends in the language, and these terms will serve as common denominators, as categories or buckets and they may become your tables in QuickBase. All of this do this already every day – on our computers we all have created file folders to structure and organize our data so that we may search and retrieve what we're looking for quickly, and efficiently. This exercise is going to help us identify the tables we will use in QuickBase. After categorizing all of your data into their appropriate groups, let's now turn our attention to relating these groups to one another. This is sometimes referred to as determining the cardinality in your data model. This is a practice in identifying the table-to-table relationships that help structure your data, commonly the "1-to-Many" we articulate when building a new relationship in QuickBase. You will want to simply say out loud what the possible relationships are, because as you listen to yourself state these out loud, it will be clear to you which 'direction' each relationship should be. Many folks are eager to get started and jump right into QuickBase and begin building, without taking the time to plan their application. This will inevitably lead to some mistakes, and the applications can quickly grow out of control as more functionality is added and the app evolves over time. This can make applications difficult to manage as they become more complex. Taking the time to plan out your application will help guide you as the needs of the system grow and more tables are included in the solution. Creating an effective data model not only benefits you in building new apps from scratch, but also is invaluable in reverse engineering an application you've inherited. Take the time to create an effective data model, it will pay dividends in the future! ------------------------------ Sean Padian ------------------------------7Views1like0Comments