(Pipelines) Get Users in Role / Process XML from HTTP API
Hello, any help/advice would be much appreciated. I'm trying to send a reminder email to users in a specific Role, in a specific App, using Pipelines. As far as I can tell, there is not a JSON RESTful API call that does this (Get Users only returns all users for an App, with no info on Roles). However, API_UserRoles returns each user from an app with what Roles they have. In theory, I could somehow loop over this and send the email to only those users with a specific role. I can successfully use the Quickbase Channel -> 'Quickbase APIs' -> 'Make Request' step to call API_UserRoles and get this data. Here's where I run into trouble: How do I process this XML into a form that another step could use (e.g. loop over it and send emails)? I found this question: "To capture an XML response from an API in Pipelines" but I can't seem to figure out how get {{a.json.qdbapi.value}}. When I try to view its contents (emailed to myself) it is blank. There isn't any "Result" field or something like that from this request step available in subsequent steps. Only URL, Method, Headers, Content Type, & Body. For instance, if I want to get the JSON out of the XML (using {{a.json.qdbapi.value}}) with the JSON Handler Channel -> 'Iterate over JSON Records', the 'JSON Source' field states 'No json sources in the pipeline' Thank you for any help you can offer, ~Daniel ------------------------------ Daniel ------------------------------
Help Needed with Quickbase Pipeline to Accumulate Values Instead of Overwriting
Hi Quickbase Community, I am facing an issue with a pipeline designed to add quantities to an existing field in my Quickbase app, but it keeps overwriting the existing values instead of accumulating them. Context: Tables Involved: Transactions: Records of items being added or removed from containers. Containers: Contains fields for tracking quantities of different items in specific compartments. Fields Involved: Transactions Table: Action Type: Indicates the type of transaction (e.g., "Add Item to Container"). Container Compartment: Specifies the compartment (e.g., "Compartment A"). Container ID: The ID of the container to which the item is being added. Item Name: Name of the item. Item Quantity: Quantity of the item being added. Containers Table: Compartment A Quantity: Field to store the quantity of items added to compartment "Compartment A". Current Pipeline Configuration: Trigger: On new or modified records in the Transactions table where Action Type is "Add Item to Container". Condition: The compartment is "Compartment A". Lookup Step: Fetch the current value of Compartment A Quantity from the Containers table. Update Step: Add the new quantity to the existing value of Compartment A Quantity. Issue: Despite various attempts, the Compartment A Quantity field in the Containers table is being overwritten with the new quantity instead of adding the new quantity to the existing value. Here is the current Jinja expression used in the update step: jinja {{ (b["Compartment A Quantity"] | default(0) | int) + (a["Item Quantity"] | int) }} Steps I Have Taken: Verified the field types and names. Ensured the pipeline permissions are correct. Tested with different variations of the Jinja expression to accumulate values. Checked pipeline logs for errors or issues. Request for Assistance: I am looking for a solution to ensure that the Compartment A Quantity field accumulates the new quantity with the existing value, rather than overwriting it. If anyone has faced a similar issue or has any suggestions on how to resolve this, your help would be greatly appreciated. Thank you in advance for your assistance! Best regards, Tom
Last Triggered Timestamp
Hi, I started migrating automations to pipelines. Yesterday, I could easily access the timestamp indicating the last triggering of a pipeline directly on the table. However, as of today, I am not able to see on this table anymore. The only method to view the last triggered time is by clicking on the three dots and navigating to "View Activity." Is this a potential problem for our pipelines?
Pipelines and Filters
Hello, I'm attempting to setup a Pipeline which checks to see if a record has two Numeric Summary Fields which equal each other, and if they do, it updates a multi-text status field from "Assigned" to "Delivered." When attempting to create the Pipeline, I've been struggling to get it to run. When attempting to set the filter so that it checks if Field A equals Field B, it seems like I can't check Field A against another field specifically, only enter a value of my own. I thought about getting around this by using a checkbox formula on the record which says if Field A = Field B, true and then having the Pipeline filter be setup such that it runs when the Checkbox field is true. However, the Pipeline never seemed to trigger off that Checkbox, even when it was changed from unchecked to checked. Is the issue that I'm not actually updating the record, but instead Summary fields which are being updated? If so, is there any way around that? Thank you in advance.
New form "email" option, automate?
Hi Everyone, I'm looking to automate via pipeline a way to email a form just like the new option when viewing a form (see attached pic). I'm not sure it's possible and I tried searching for a solution in the discussions. I know this feature is relatively new and thought I'd reach out to see if anyone has the same interest. I'm more interested in using the native "email" function like below than using GMail but if there's no other way, I'll pursue that route instead. Thanks!
When the Expiration Date is On or Before Today, Change the Contract Status to Expired
Hello: I have a contract application. Goal: When the Contract Expiration Date field is on or before today, and the Exception to the Expiration Date Dynamic Form Rule field is unchecked, I want theContract Status field to automatically change to Expired. Question: What is the best method to accomplish the above goal, form rule, text formula, or pipeline? 1. I tried the below form rule. However,it works intermittently. I still see expired contracts that show as active 2. I created a formula - Text field named Contract Status Formula, but I am unsure whether my formula is correct. If( Today() <= [Contract Expiration Date], "Expired") 3. I tried to create apipeline. My first attempt was to Search Records/Update Record. My second attempt was to On New Event/Search Records/Update Record. However, I know I am missing a step. Any step-by-step guidance would be greatly appreciated. Thank you, RoulaParse JSON
If you are looking to parse a JSON response in a Pipeline and you know where and what value are looking for there is a simple way to get to a specific piece of data. Credit for this goes to Jenny on the QB Support Team for getting me the solution. There are five parts to the Jinja Expression The STEP that the JSON is resident in The SECTION of the JSON to get What part of the ARRAY to get The FIELD to get The value Here is the expression {{STEP.json.SECTION[ARRAY]['FIELD'].value}} So here is what my JSON looked like { 'data': [{'3': {'value': 14}}], 'metadata': {'updatedRecordIds': [], 'createdRecordIds': [14], 'unchangedRecordIds': [], 'totalNumberOfRecordsProcessed': 1}} {createdRecordIds} } This is a really small array. In the 'data' section is only one piece of data for FID3 and its value is 14. That is what I wanted to get. So my working Jinja Expression is {{b.json.data[0]['3'].value}} The JSON was coming from Step B. data is the section I want to get something from. There is another on it called metadata but I am not interested in those at the moment. 0 is the first part of the array. If your JSON returns ten records JSON counts to ten by going: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 3 is the name of the information I want. The real world case here is that I asked for the value of FID 3. In QB the name of the field would be Record ID but the name is not what got returned it was the FID value tells it to give me the value for '3' The answer that the Pipeline Step kicks out is 14 which is exactly what I needed for the next part of my problem. If you have large arrays, need to search for data or manipulate the result further, this is probably not helping much. If you know where and what you want to pull from the JSON, it will do the trick.Parse JSON
If you are looking to parse a JSON response in a Pipeline and you know where and what value are looking for there is a simple way to get to a specific piece of data. Credit for this goes to Jenny on the QB Support Team for getting me the solution. There are five parts to the Jinja Expression The STEP that the JSON is resident in The SECTION of the JSON to get What part of the ARRAY to get The FIELD to get The value Here is the expression {{STEP.json.SECTION[ARRAY]['FIELD'].value}} So here is what my JSON looked like { 'data': [{'3': {'value': 14}}], 'metadata': {'updatedRecordIds': [], 'createdRecordIds': [14], 'unchangedRecordIds': [], 'totalNumberOfRecordsProcessed': 1}} {createdRecordIds} } This is a really small array. In the 'data' section is only one piece of data for FID3 and its value is 14. That is what I wanted to get. So my working Jinja Expression is {{b.json.data[0]['3'].value}} The JSON was coming from Step B. data is the section I want to get something from. There is another on it called metadata but I am not interested in those at the moment. 0 is the first part of the array. If your JSON returns ten records JSON counts to ten by going: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 3 is the name of the information I want. The real world case here is that I asked for the value of FID 3. In QB the name of the field would be Record ID but the name is not what got returned it was the FID value tells it to give me the value for '3' The answer that the Pipeline Step kicks out is 14 which is exactly what I needed for the next part of my problem. If you have large arrays, need to search for data or manipulate the result further, this is probably not helping much. If you know where and what you want to pull from the JSON, it will do the trick.JSON Parse from QB Response
If you are looking to parse a JSON response in a Pipeline and you know where and what value are looking for there is a simple way to get to a specific piece of data. Credit for this goes to Jenny on the QB Support Team for getting me the solution. There are five parts to the Jinja Expression The STEP that the JSON is resident in The SECTION of the JSON to get What part of the ARRAY to get The FIELD to get The value Here is the expression {{STEP.json.SECTION[ARRAY]['FIELD'].value}} So here is what my JSON looked like { 'data': [{'3': {'value': 14}}], 'metadata': {'updatedRecordIds': [], 'createdRecordIds': [14], 'unchangedRecordIds': [], 'totalNumberOfRecordsProcessed': 1}} {createdRecordIds} } This is a really small array. In the 'data' section is only one piece of data for FID3 and its value is 14. That is what I wanted to get. So my working Jinja Expression is {{b.json.data[0]['3'].value}} The JSON was coming from Step B. data is the section I want to get something from. There is another on it called metadata but I am not interested in those at the moment. 0 is the first part of the array. If your JSON returns ten records JSON counts to ten by going: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 3 is the name of the information I want. The real world case here is that I asked for the value of FID 3. In QB the name of the field would be Record ID but the name is not what got returned it was the FID value tells it to give me the value for '3' The answer that the Pipeline Step kicks out is 14 which is exactly what I needed for the next part of my problem. If you have large arrays, need to search for data or manipulate the result further, this is probably not helping much. If you know where and what you want to pull from the JSON, it will do the trick.
