Join multi-line text field to one line
Hi all. I'm trying to find a way (either using a formula or in Pipelines) to join a multi-line text field to a single line. Use case: The multi-line text field will contain text that will go to the JSON request body of an API call in Pipelines, so the field needs to be converted to a single line. The field has to a multi-line text field, because values can contain several paragraphs and app users can easily customize it. Thanks!Time of Day field values are not in 24-hour format in Pipelines
Hi all. I think I found a bug with Pipelines where using a Time of Day field isn't in 24-hour format even when you set the field settings to 24-hour. Can anyone think of a possible workaround? Most APIs use 24-hour format so having Pipelines only output in North American format makes it impossible to pass along the correct time format. Steps to reproduce: Create a Time of Day field. In field settings > Value display, enable 24-hour clock. Create a pipeline that sends a value in this field. Pipelines outputs the field in North American time format (for example, 5:00 PM), instead of 24-hour format (ex: 17:00). I tried using Jinja to reformat to 24-hour, but Pipelines doesn't support the jinja filters needed to re-format to 24-hour time. Here's the Jinja expression I tried: {{ time-field|replace(" AM", "").|replace(" PM", "")|stringptime("%I:%M")|strftime("%H:%M") }}Date value changes when copied to new table with pipeline.
I am updating an app with a [Fines] table that has 10 pairs of Pmt-Dt-* and Pmt-Amt-* fields. The date fields are Date (not Datetime). 1) I created a new [Payments] with Fine-ID, Pmt-Dt, and Pmt-Amt fields. The new table will support online payments, so we want the new Pmt-Dt field to be Datetime to differentiate between multiple payment attempts on the same day. 2) I created a pipeline to read each Pmt-Amt-* of each record. If Pmt-Amt-* > 0, then the pipeline inserts the payment into the [Payments] table. ISSUE: Although both tables are in the same application, the new [Payments] table dates are created with a timezone adjustment. The application is UTC-05:00 (Eastern US & Canada). • 2012-02-02 (in original Fines table) is inserted as 2012-02-01 19:00 in the new table (5 hours earlier). • 2018-08-08 (in original Fines table) is inserted as 2018-08-07 20:00 in the new table (4 hours earlier, during DST). I can probably use time.delta(hours=5) and time.delta(hours=4) to update the original values, but this will require identify the exact spring-forward and fall-back dates for each year with payments. Is there a better, more automated solution?
Pushing JSON data to external API endpoint
Hello, I haven't been able to find any instructions anywhere on how to setup a Pipeline to push JSON data to an external API endpoint. Ideally, I want to send JSON data to an external API endpoint when a record is created, or modified via pipelines. I was able to set this up with a Webhook, but Pipelines doesn't seem as obvious. Thanks, JamesJira Assignee
Good morning, I've created a pipeline to create a Jira story when an issue record is created in QuickBase. Most of it is working, but I can't seem to get the Assignee and the Reporter fields to work. I'm thinking it is because they are user fields? Is there something I need to do to convert the QuickBase data to what Jira needs in these user fields? I've tried using each of the options (email, first/last name, screen name) but it just appears as blank in the Jira ticket. Thank you!
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?Updating predecessors in a pipeline
Hi all, I am creating templates for our projects that contain a set number of tasks done in a specific order. I want to use a pipeline to create and schedule tasks when a new project is created. I'm running into a roadblock where I can't figure out how to keep the predecessors of the tasks so we can set a start date when the project is created, and it will populate all future task dates. I hope that makes sense. The pipeline is working fine to create the tasks, but I can't figure out how to set the predecessors. Here is my table structure (simplified): [TABLE] Template Projects - Project Name [TABLE] Template Tasks - Task Name - Duration [TABLE] Template Project/Tasks Associations - Related Project - Related Task - Predecessors [TABLE] Project - Select Template (Related Template Project) - Start Date [TABLE] Tasks - Related Project - Task Name - Duration - Start Date - Project Finish - Predecessors (Please be kind, I am new to this) Thanks in advance!
Pipelines and appending / joining
I have a jinja expression that simply compares old to new, and writes to the text field it sits in on the pipeline: {% set result = "" %} {% if a.requested_offer_types != a.$prev.requested_offer_types %} {% set result = result + "Requested Offer Types from " + a.$prev.requested_offer_types + " to " + a.requested_offer_types + "\n" %} {% endif %} {{ result }} The if works however it overwrites the text field. I want it to append to the text field. I dont want to use the log function, as I dont need the user and time details
Outlook pipelines trigger off multiple calendars in a single mailbox?
Having an issue with pipelines and multiple calendars in a single mailbox. I can get calendar events created/updated/deleted into a table with a single calendar, and am using the id of the event to track unique records. I'm finding in the pipeline activity that event ids aren't feeding into the pipeline with unique values, but the create/update/delete is working somehow anyway with one calendar. Does Quickbase track uniqueness of outlook events somewhere behind the scenes? It works so I'm not complaining too much on this one. My actual question...Adding a second pipeline, pointed at a different calendar in a mailbox doesn't trigger the additional pipeline at all. Is this possibly a bug? This function reads like you can connect multiple calendars from the same mailbox.
