How to verify email has been sent w/ Outlook Send an Email
What is the best way to verify that an email was sent using the Outlook channel's Send an Email step? I would like to update a record's status to Sent after I've verified that it's associated email has been. I don't see a way to reference the email's status or id after the Send Email step. I have tried a few things - 1. After sending the email, use the Search Emails step to find the email in the Sent folder. I create a secret key, put it in the email's body, but can't get this to work. I receive only the error: Validation error: {'query': 'required field'}. 2. We have the Sent folder already set up as a Connected table. I could force the table to refresh and then look it up there. There could be several emails being sent within the pipeline run, and I would have to do this in a loop which isn't ideal. Any other ideas on how to verify an email has been sent using the Outlook Send an Email step?
Need help with nesting statements for pipeline
I have two template tables that are related (Task template - parent and Subtask template - child). Both of these tables have a multi-select field called Task Category which could list property purchase, business purchase, lease, ground lease, construction, property sale, business sale as some tasks apply to multiple types of transactions. I also have the option of All if the task applies to any type of transaction. A transaction can involve several options - for example we could purchase the property and construct a building, or we could purchase a property and lease to a tenant. Upon the trigger of the pipeline, the appropriate Tasks are copied from the Task Template table to the Task table based on matching criteria. It works but I don't know how to add a 2nd step to also pull any tasks that are marked "All". I've attempted to add it within this statement as well as using AND but it errors . This is my current formula: {% set list = a.deal_task_category.split(';') %} {% for item in list %} {% if loop.last %}{9.HAS.'{{item}}'} {% else %} {9.HAS.'{{item}}'}OR{% endif %} {% endfor %} I have a similar issue in next step for the subtasks. For this step I have three functions that I need to accomplish (1. I need to pull the Subtasks that relate to the copied Tasks (which I attempted to do in the first line in the formula below), 2&3. do the exact same as above - pull over the subtasks that match the Task Category and then pull over any subtasks that have "All". This is what I attempted but it gives "Valueerror: invalid literal for int() with base 10: 'id' {{h.template_id == i.related_test_task_template}} AND {% set list = a.deal_task_category.split(';') %} {% for item in list %} {% if loop.last %}{25.HAS.'{{item}}'} {% else %} {25.HAS.'{{item}}'}OR{% endif %} {% endfor %} Any insight on how to add nesting request would be much appreciated!Records, Pipelines, and Callable Pipelines clarification
Hello! I am a new user, and I'm looking for some clarifications on some of the specifics about how records, pipelines, and the callable pipelines action relate. I have a complex pipeline trigger by a user record creation. The pipeline runs through a substantial decision tree and updates records and sends notifications depending on the path through the decision tree the record takes. However, I have run out of actions and need to set up a callable pipeline to do some record validation (instead of adding those steps into the main pipeline). So, I am working on setting up the callable pipeline, but I want to make sure that the pipelines are only updating a given record, and not ALL records. - Update: before you read the next part of the post, consider that I may be overthinking this whole thing and I just need to pass through the record ID(s) for the records I want my called pipeline to validate. - I assume that when a pipeline runs with the "record created" trigger that the pipeline will run only with relation to a given record; i.e. is the context of the pipeline run a single record? Is that correct, or does it evaluate the whole table of records? Or do I need to set a record limit on the trigger? When I use a callable pipeline, does the calling pipeline maintain the context of the call; i.e. for a single or batch of records? Depending on that answer, does the pipeline evaluate each of those records individually, or does it evaluate the entire table with respect to the called field(s)? For example, here are my two actions. I thought I had them set up correctly, but I can't call the fields from the calling pipeline in the called pipeline (third screenshot). Update: this may be because neither of the pipelines are turned on, and I may be using Jinja expressions where I should instead be using aliases which I can set to the calling pipeline's fields (see this video). Do I need to bother with passing the record IDs ("a.id"), or are those "implicit"? Call action: Called trigger: Not finding called fields: BUT let's assume that I get these calls to work. Will the changes to the records made in the calling pipeline have been written to the table when the called pipeline is called? Because that pipeline will need to do evaluations based on the records' data, which is dependent on the actions in the calling pipeline! Thanks for all of your help!
Date / Field stamp through pipeline
I have a step in my pipeline that creates line items and inserts required data in that line item. The completion status of this line item is dependent on the field completed date. How do i include the completed date in the step so that when the data is added so that the line item is complete
Pipeline formula for user names
I need a pipeline to populate a field in a new record with the names from another field. Many users did not update their profile with a ‘Screen Name’ so I can’t use that field in the pipeline. I am having trouble getting it to populate using the First and Last Names. What formula can I use in Pipelines to create a list of multiple names? I used this field to create a text field and this is what is returned: Using this text field is not ideal as Barb does not have a screen name so it defaults to her email address. If there are several users, this field will be harder to read with emails being used. I want the pipeline to take the Fundraisers Assigned values and populate like this – preferably comma separated but semi-colon is fine too. Example: Amy Gosz, Barbara Burns I can get the First Name and Last Name to combine but then it only returns one of the names. How do I write the formula to not only combine the First Name and Last Name, but also list the multiple users names? I need all names (can be several) that appear in the Fundraisers Assigned field to populate to the new field.
Do Bulk Records Pipelines Make Simultaneous Updates?
When bulk records are handled in a pipeline, are all of the applicable records updated simultaneously? Will they have the same modified date and time? I have notifications setup to be triggered when a date field is updated. I have a formula checkbox field used to identify the most recent record associated with an email address field value. The most recent record may not be the one that gets updated along with other records with the same email address field value. I don't want the email notification being sent before other associated records are updated. I am looking at using Bulk Record steps to reduce the number of pipeline steps I am currently using as well as handle everythingmore efficiently. I just need to know if I would be safe having the date field updated on the most recent record with the other potential changes without worrying about the email being triggered before all applicable updates are made. Thank you, in advance for any input. Let me know if I need to provide a visual and/or more clarification on what I am looking to accomplish.
PIpeline - split multiselect and create records from it
I can't seem to wrap my head around this. I have a record with a multiselect field. When conditions are met, I want a pipeline to take data from the record and create a new record in another table, creating one record for every value in a multi-select field. I can't seem to figur eout where I would put the jinja to split those values and then loop through them. Googling came up with the following for the Jinja: {% set selected_values = a.your_multi_select_field | split(';') %} But where would I put this? Seems like I need a step after my trigger to do this, but there isn't a "jinja" channel.Could not parse XML input
Hi, I'm getting errors on my pipelines for a multi-line field. Quickbase reported an error: 11 : Could not parse XML input : XML Parsing Error. not well-formed (invalid token) at line 3 column 353 (which is byte 700) When I look through the activity log and the original db i'm seeing these characters: †and “. When I talked with the users they said they did not put them in the field. After a little research it looks like it was a copy and paste issue. My question is how can i prevent this from being sent through the pipeline? Thank you
Pipeline help
I have a parent table called principal investigators (PI) that has a child table called "applications". This is for external users to apply to a grant we are hosting, all the information will come through a form in the applications table. However, I want to pull information from the applications table into the PI table for future querying. Very simply, users will put in their name, email address, and departmental affiliations which I want to then create a record in the PI table if it does not exist. If it does exist, I want to update the applications table with the related PI record ID. I cannot get this to trigger properly and I have tried many times. It fails at the IF/ELSE statement. Here is my YAML file below if it helps (I removed identifying information): # Add PI to table # # Account slugs: # - quickbase[DB]: Realm Default Account <None> --- - META: name: Add PI to table enabled: false - TRIGGER quickbase[DB] record on_create -> a: inputs-meta: allow_triggers: Any export_fields: '"Applicant Name, Applicant Email, Departmental Affiliations, Related Investigator" <6, 9, 81, 234>' table: '"Awards Portal: Applications" <##>' - QUERY quickbase[DB] record search -> b: inputs-meta: export_fields: '"Email Address, Full Name" <7, 6>' table: '" Awards Portal: Principal Investigators" <##>' name: Search for records in PI table note: Search for records in PI table that match the applicant email - b<>LOOP: - DO: - IF: - AND: - a<>applicant_email equals {{b.email_address}} - THEN: - a<>ACTION quickbase record update -> c: inputs: related_investigator: '{{b.id}}' name: Update the record note: This step updates a record in the table - ELSE: - ACTION quickbase[DB] record create -> d: inputs-meta: export_fields: '"Affiliations, Email Address, Full Name" <8, 7, 6>' table: '"Awards Portal: Principal Investigators" <DB>' inputs: affiliations: '{{a.departmental_affiliations}}' email_address: '{{a.applicant_email}}' full_name: '{{a.applicant_name}}' name: Create the record note: This step creates a record in the table - a<>ACTION quickbase record update -> e: inputs: related_investigator: '{{d.id}}' name: Update the record note: This step updates a record in the table - metadata: name: If a condition is met, do something note: Check if condition is true - metadata: name: Iterate through the records note: Iterate through the records found in the previous step ...
