Pipelines bug: Not able to parse JSON when JSON records path defined
Hello, I bought up this very issue 2 years ago, but it now looks like the solution is no longer working. https://community.quickbase.com/discussions/quickbase-discussions/pipelines-bug-json-value-not-being-parse-when-specifying-the-json-records-path/20129 Steps to reproduce: Insert a fetch JSON and iterate JSON steps. In the Iterate JSON step, I've defined the JSON Records Path as: /response/results. I've included an example JSON response below. Inside the Iterate JSON loop, I'm tried using the following variables to refer to the custom_id parameter: {{c.raw_record.custom_id}} {{c.raw_record.['custom_id']}} However, I keep getting this error when the pipeline is run: Validation error: Incorrect template "{{c.raw_record.custom_id }}". ValueError: invalid literal for int() with base 10: 'raw_record' This is very strange as this method to refer to a JSON path used to work perfectly. I also doubled checked the activity log and using raw_record in the variable should be correct, because when you define the JSON Records Path, Quickbase uses "raw_record" to refer the defined path as shown in the activity log for the Iterate JSON step with the records path defined. (see attached screenshot) Example JSON response { "status_code": "200", "response": { "batch_id": 123", "created_at": "1740504520", "expires_at": "1740590920", "completed_at": "1740504923", "status": "completed", "results": [ { "custom_id": "123", "result": { "text": "text", "type": "text" } }, { "custom_id": "test_0", "result": { "text": "text", "type": "text" } } ] }, "error_message": null }
Document Template creation - Save PDF to field in record
Hi, I basically imported the following YAML. And everything is looking ok until it comes to the Body of the “Save File to a Table” Where I am getting a “This field contains invalid jinja references” error. Thank you so much for helping! Below is the Body (image also below): { "to": "bts4ydgrs", "data": [ { "340": { "value": { "fileName": "{{a.json.fileName}}", "data": "{{a.json.data}}" } } } ], "fieldsToReturn": [] } } } ] } "fieldsToReturn": [] } The Below is the YAML I imported: # Doc Gen Testing # # Account slugs: # - quickbase[CHANGE ME]: Realm Default Account <None> # - microsoft-outlook[CHANGE ME]: # <None> --- - META: name: Doc Gen Testing - ACTION quickbase[CHANGE ME] quickbase_api make -> a: inputs: method: GET url: https://api.quickbase.com/v1/docTemplates/1/generate?tableId=DBID_CHANGE_ME&format=pdf&pageSize=Letter&filename=Invoice&margin=1 1 1 1&unit=in&orientation=portrait&recordId=1 name: Generate Doc - ACTION quickbase[CHANGE ME] quickbase_api make -> b: inputs: body: "{\n \"to\": \"CHANGE_ME_TABLE_ID\",\n \"data\": [\n {\n \"6\"\ : {\n \"value\": {\n \"fileName\": \"{{a.json.fileName}}\"\ ,\n \"data\": \"{{a.json.data}}\"\n }\n \ \ }\n }\n ],\n \"fieldsToReturn\": []\n }\n }\n }\n \ \ ]\n}\n \"fieldsToReturn\": []\n }" method: POST url: https://api.quickbase.com/v1/records name: Save File to a Table note: 'Write the record ' - LOOKUP quickbase[CHANGE_ME] record look_up -> c: inputs-meta: table: '"Demo App: Invoice Files" <CHANGE_ME>' export_fields: '"File" <6>' inputs: id: '{{b.json.metadata.createdRecordIds[0]}}'Move attachment to SharePoint error
I'm trying to set up a pipeline to move a file attachment to a folder in a SharePoint when a record is created. On the SharePoint step, I'm getting this error. Does anyone know what is causing this? Remote API returned authentication error: (invalid_grant) AADSTS700003: Device object was not found in the tenantDocument Template Save PDF to field in Record API Pipeline
I have been wracking my head all day on this. I was reading Generate Documents from your records in your app where it says "However, you can also create API calls and use Pipelines, code pages, or custom integrations to generate documents. Each part of the formula represents an API parameter.". I was using Restful "Generate a Document" and was able to make a request: How do I get the output of making a request or basically the document template for this record as a file attachment in the record? I tried using: <qdbapi> <rid>1700</rid> <field fid="22" filename="Model_T.jpg"> Base64 encoded file content</field> Thank you so much!
Auditing field changes using Pipelines & Jinja
I'm using Pipelines to track changes on hundreds of fields in a table. The step that writes a summary of the changes to a rich text field uses Jinja that looks like this: {% set fields = [ ('Field Name 1', a.field_name_1, a.$prev.field_name_1), ('Field Name 2', a.field_name_2, a.$prev.field_name_2), ... ('Field Name 200', a.field_name_200, a.$prev.field_name_200) ] %} {% for i in fields %} {% if i[1] != i[2] %} {{'• <b><u>' ~ i[0] ~ '</u></b> changed from <b>' ~ (i[2] if i[2] is not none else '(null)') ~ '</b> to <b>' ~ (i[1] if i[1] is not none else '(null)') ~ '</b><br />'}} {% endif %} {% endfor %} It works, however I'm questioning whether this can be done more elegantly, with Jinja or otherwise. I couldn't find a way to loop over the changed fields only in a generic fashion so I constructed tuples for each field. This makes the step very lengthy and difficult to find what I need; additionally my browser becomes sluggish when working with the Pipeline. I appreciate any recommendations here.
Unable to insert a row in Sharepoint List
Friends, I have a SharePoint list with book data. I have built a pipeline in quickbase that will insert a new row in the list whenever a new record is created in quickbase I have created the connection to my SharePoint list correctly. It identifies the site and the list. But the pipeline is unable to add a record in Sharepoint. I keep getting these errors consistently. What am I doing wrong? I am new to Sharepoint integration with Quickbase. Please help.
Can't connect pipelines to personal email account in order to send a scheduled notification.
Quickbase automations used to let me send an email directly from the Quickbase app, and the notifications option still lets me do this. However, If I want to schedule a notification on any basis other than record added, deleted or modified, it tells me I need to use a pipeline. Then in pipelines the only email actions are through 3rd party email services that I would have to give Quickbase my sign-in to use. There are two problems with this; I use my email to send encrypted private and regulated data and cannot simply let Quickbase have access to read and send my emails on my account without going through a bunch of extra red tape. I do not want Quickbase automated emails to originate from my personal email address as if I am sending them. Our email domain occasionally changes, and I will not always be with the company, when I leave, my email address will be deactivated, so the pipeline will be terminated. Does anyone have a workaround?How to Pull Employee Name and Title Instead of Record ID Number in Quickbase Pipeline
Hi Quickbase Community, I'm working on setting up a pipeline that will create a record in an archive app. I want to pull over the employee name and title into the new record, but the only available option I have is the Record ID. Unfortunately, when I use the Record ID, it only brings over the number ID rather than the actual name, and there is no title option at all. How can I pull the employee name and title instead of just the Record ID? Thanks in advance for your help! Meagan
