Conversion from textlist to text?
I'm trying to write a formula for two fields-- Field 1 has Option 1 and Option 2. I'm trying to configure it so that if the user selects Option 2, then another field will pop up for them to answer. Right now, my formula works because I have Field 1 set as a Multiple Choice field type. However, I need Field 1 to be a Multi-Select field type, and when I try to change it to a Multi-Select, then my formula does not work. I get this error: Invalid formula provided in form rules: [{"errorMessage":"Formula Error -- Type MismatchThe expression [_fid_18] on the left hand side of the operator \"=\" is of type textlist while the expression \"Vendor\" on the right hand side is of type text.","ruleIndex":11}] What's the best way to implement this?
Working with %%rid%% and checking a box
I know this has been probably answered before, but I just can't get this formula to work. I want it to save a record (even a new record or already created one) and check a box. I am going to use that box in a pipeline. Here is my formula. Can anyone see what I am doing wrong? It does not check the box (fid is 599). var text RID =If(IsNull([P-Referral Record ID#]),"%%rid%%", ToText([P-Referral Record ID#])); var text URL = URLRoot() & "db/" & Dbid() & "?a=er&rid=" & $RID & "&_fid_599=1"; var text LABEL = "Send Consent to JotForm"; "<a class='Vibrant Success SaveBeforeNavigating' data-replaceRid=true href='" & $URL &"'>" & $LABEL & "</a>"
Formula to populate a field based on another field that contains a specific text string?
I'd like to have a field on a form automatically populate based on if a specific text string exists inside of another field. Let say field 2 will be populate with the text "red squadron" if field 1 contains the text "red". Can I do this with a formula using contains or would I need to create a table where all possible combinations that contain the text "red" would align to being in red squadron?
In-App Formulas - Removing Duplicates From A List or String
I'm working on a formula to concatenate values from multiple multi-select text fields while removing any duplicates in the output. My goal is to create a unique, semicolon-delimited list that’s easy to process further. Here’s a breakdown of the fields I’m working with: [Related Modification - Operator Access] [Related Project - Operator Access] [Related Phase - Operator Access] [Note Replying To - Operator Access] [Related User - Affiliation] Quickbase’s formula language doesn’t support loops, assignments, or a direct Unique() function to filter out duplicates. Here are some of the approaches I’ve tried: Using Conditional If Statements I set up If statements that check each field’s value with Contains to see if it’s already present in the accumulating list. While this approach works in theory, I have been having trouble with type and syntax errors. It also quickly becomes verbose and difficult to maintain as the list of fields grows. var text initialList = ToText([Related Modification - Operator Access]); var text withProject = If(not Contains(ToText(initialList), ToText([Related Project - Operator Access])), List("; ", ToText(initialList), ToText([Related Project - Operator Access])), ToText(initialList)); ... and so on for each field Using List and Split Functions with Unique() Equivalent I attempted to split the concatenated list and simulate unique functionality by adding fields conditionally. Unfortunately, Quickbase lacks a direct Unique() function for removing duplicates from lists, so this approach didn’t work as expected. Help Requested Has anyone found an efficient way to concatenate and de-duplicate multi-select text fields in Quickbase? Ideally, I’d like a solution that’s concise, scalable, and doesn’t require manually adding each field with repeated If and Contains checks. Are there workarounds, or perhaps Quickbase functionality I’m overlooking, that could streamline this task? I would much prefer to keep the processing in the table as it pulls from other tables where the data can change. So it needs to be quite responsive and I don't want to have to declare an excessive amount of triggers. Any insights, examples, or alternative approaches would be greatly appreciated!How should I set up this Formula URL button
I’ve been trying to set up a notification email for approvers, where when a leave request is submitted by a faculty member, approvers receive the email notification that there is a leave request pending that they then need to approve or deny. The email text will be pulled from a form I’ll create including approve/deny buttons. My problem is the two tables that hold the approve/reject statuses: REQUEST DECISIONS and DECISION STATUS CHANGES, which you helped set up by having REQUEST DECISIONS be the table containing the single approval record for each approver for each request and the DECISION STATUS CHANGES table contain all status records over time (ie: pending/approved or rejected). I’m not sure how the process for the buttons would work correctly. Should I: Create Formula-Rich Text button fields that use API_EditRecord from related REQUEST DECISIONS RID and then add copy of this info to new record in DECISION STATUS CHANGES or Create Formula-Rich Text button fields that uses API_AddRecord to add a new record to the DECISION STATUS CHANGES (akin to the Add Form Temp form you created in this table) I asked chatgpt what it thought and this is what it came up with. Do you agree? For your notification and status update setup, both approaches could work, but each has its advantages. Here’s a breakdown of the two options: 1. Using API_EditRecord in REQUEST DECISIONS How it works: A Formula-Rich Text field with API_EditRecord could be used to directly update the status in the REQUEST DECISIONS table, making it easy to capture each approver's decision (approve/reject) for a specific request. After updating REQUEST DECISIONS, you could use an additional API_AddRecord action to copy the status change details into the DECISION STATUS CHANGES table for historical tracking. Pros: Directly updates the status in REQUEST DECISIONS, so you can see the current status for each approver in one place. Easier to manage a single source of truth for each approver's decision. Cons: Requires an additional step to create a historical log in DECISION STATUS CHANGES. 2. Using API_AddRecord in DECISION STATUS CHANGES How it works: Here, you would create Formula-Rich Text button fields that trigger API_AddRecord actions to add a new status change record to the DECISION STATUS CHANGES table directly. Each time an approver makes a decision, a new record in DECISION STATUS CHANGES will capture the action, with fields indicating the approver, request ID, and decision. Pros: Automatically generates a history of all status changes without needing extra steps. Each decision action creates a new entry, making it simple to see all status changes over time. Cons: Would require additional queries or formulas to retrieve the current status for each approver since DECISION STATUS CHANGES would hold multiple records per request. Recommendation To streamline the workflow while maintaining both current and historical statuses: Use API_EditRecord in REQUEST DECISIONS to update the status directly when an approver takes action. Immediately after, use API_AddRecord to insert a new record into DECISION STATUS CHANGES to log the decision. This approach leverages the strengths of each table while ensuring that both the current status and historical log are maintained. The Formula-Rich Text buttons can trigger both API calls sequentially to achieve this without user intervention.
