ContributionsMost RecentMost LikesSolutionsRe: Color Coding based on field value I believe that's due to an empty span and the inline display. Try this: <span style='background-color:red;display:block;'> </span> Re: Working with JSON Array in Pipelines If you use the "Fetch JSON" step in the "JSON Handler" channel instead, then you can use the "Iterate over JSON records" step to loop the records. Re: Fomatting Date returned in Json Response Ahh, it's missing the conversion from string to date/time and the field type was incorrect. Try this: {% elif field['type'] == 'date time' -%} <td>{{ time.parse(record[field['id'] | string]['value']) | date_mdy }}</td> Re: Fomatting Date returned in Json Response If the field includes the date and time, the field type is 'timestamp', otherwise it's 'date'. So you could add: {% elif field['type'] == 'timestamp' -%} <td>{{ record[field['id'] | string]['value'] | date_mdy }}</td> Re: Left function stripping on first "-" rather than "-O" as written NotRight("JKL-6-O", "-") will split at the last delimiter and returns "JKL-6" Re: (Pipelines) Get Users in Role / Process XML from HTTP API I should have mentioned you would need to change that line too, but happy to hear it's working now! There is some help on using Jinja in Quickbase: https://helpv2.quickbase.com/hc/en-us/articles/4471048652308-Using-Jinja-in-Quickbase-Pipelines That page also has a link to the Jinja documentation: https://jinja.palletsprojects.com/en/2.11.x/ Re: (Pipelines) Get Users in Role / Process XML from HTTP API Hi Teresa, no worries happy to help! I see from the screenshot that your query is step A and not B, so you need to adjust line 2 to "a.json.qdbapi.users.user" for it to read the data properly. Re: API_GetUserInfo You could use the Get Users API, which doesn't stop processing if a user doesn't exist. The request body can have one or more email addresses, and you'll need to use Jinja to convert the body to JSON: If the user doesn't exist, it returns an empty "users" array: Hope that helps! Re: (Pipelines) Get Users in Role / Process XML from HTTP API This code will filter the API_UserRoles output on a specified role and return the names as a semicolon-separated list: {% set searchRoleId = '12' -%} {% set users = b.json.qdbapi.users.user -%} {% for user in users if user["@type"] == "user" -%} {# Handle single vs array of roles -#} {% if user.roles.role is iterable and user.roles.role is not mapping -%} {# Array of roles -#} {% set userRoles = user.roles.role | map(attribute='@id') | list -%} {% else -%} {# Single role, return as array of roles -#} {% set userRoles = [user.roles.role['@id']] -%} {% endif -%} {% if searchRoleId in userRoles -%} {{ user['name'] }}{{';' if not loop.last }} {%- endif -%} {% endfor -%} Change line 1 to search for a different role id. The data returned from API_UserRoles is different if a user is a member of a single role vs multiple roles, so this code has the logic to handle both cases. The output will look like "John Doe;Jane Smith;Bob Jones". The output of the regex step should assign a "group_0" to each of the names that you can iterate with a loop. Hope that helps! Re: Date value changes when copied to new table with pipeline. If you add the time to the date then it should not roll back to the previous day: {{ (a.payment_date|date_ymd) ~ "T12:00" }} Creates a string like "2018-08-08T12:00"