JustinTorrence
Qrew Cadet
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: ChatGPT like search engine?
Hi Mohamed! In order to do semantic search within a Quickbase application, we would be reliant on their product team to support some type of vector database feature. Not really sure if they are tooled to build that type of capability into every customer environment, or what the performance implications would be, but that is their challenge to solve. I have been able to get this type of thing going for my own Quickbase data, but it was necessary to first replicate the data in an environment that already had support for vector storage and search. I've had some success with xata.io and their Vector Search API. I've also had some success creating my own ChatGPT app in Quickbase using OpenAI's Chat Completion API. I've uploaded the app to the exchange, but I'm waiting on Quickbase's approval. Happy to talk more about it anytime if you're interested. ------------------------------ Justin Torrence Quickbase Expert, Jaybird Technologies [email protected] https://www.jaybirdtechnologies.com/#community-post ------------------------------Re: Jira Pipelines - Cannot access custom fields
You can set it up the other way round, but that means you won't be able to use the out of the box connector. Jira has a feature called Automations that has similar functionality to Pipelines. Whenever a change to an issue meets the conditions that you are looking for in Jira, you can use the "Web Request" action and send the entire Jira object over to a Quickbase Pipeline that starts with an "Incoming Request" trigger from the Webhooks channel. You'll need to know how to use Jinja2 and their object notation navigation, but altogether this is a fairly simple automation. #Pipelines #JINJA #webhook ------------------------------ Justin Torrence Quickbase Expert, Jaybird Technologies [email protected] https://www.jaybirdtechnologies.com/#community-post ------------------------------RESTful API - groupBy
The request body of the Query for data endpoint accepts a groupBy property which is an array of object items . I understand the syntax and can follow along, but in my testing I haven't seen any measurable change in json returned in the response body no matter the pair of field/grouping I provide. The sortBy property seems to take the same parameters and returns data as expected. Has anybody had success using this property that they feel comfortable sharing? #APIsandcustomcode #reportsandcharts ------------------------------ Justin Torrence Quickbase Expert, Jaybird Technologies [email protected] https://www.jaybirdtechnologies.com/#community-post ------------------------------Re: Quickbase Pipelines: How to upsert nested JSON array to multi-select text field?
How interesting. I just had to solve this problem the other night. To get a more succinct Jinja2 expression you'll want to use combinations of following filters: selectattr map join If I understand your schema correctly, the expression for the first issue (where you are simply writing to a text field) would look like this: {{ d.custom_fields | selectattr('key', 'eq', 'street') | map(attribute='value') | join('') }} The second problem may be a little less elegant because there isn't a way that I know of to combine multiple lists using jinja2. {% for choice in d.custom_fields | selectattr('key', 'eq', 'choices') -%} {{ choice.value | join(';') -}} {% if not loop.last %};{% endif -%} {% endfor -%} The important part to remember about multi-select text is that a semicolon should be used as a delimiter (unless you are posting the data directly via the RESTful API). Here is a live parser that allows you to test with json instead of only YAML. https://j2live.ttl255.com/ ------------------------------ Justin Torrence Quickbase Expert, Jaybird Technologies [email protected] https://www.jaybirdtechnologies.com/#community-post ------------------------------Re: Undocumented Pipeline yaml functionality
Nice find! I'm curious if the references are preserved in the "Pipeline Summary" in the Activity Log. Also, I fear that they might also be lost if you use the Refresh Schemas button: ------------------------------ Justin Torrence Quickbase Expert, Jaybird Technologies [email protected] https://www.jaybirdtechnologies.com/#community-post ------------------------------Re: Button go to Filter Report
@Herberth Solano The string that comes after &query= parameter is Quickbase's query language after it has been URL Encoded. You can use an online URL Decoder to get a slightly more human readable version of this: That query parameter applies some filters to this base report: https://veinsacr.quickbase.com/db/biwugpbzm?a=q&qid=6 The filters in more readable format are: (All conditions are true) The value in Field Id 26 is equal to "Disponible" The value in Field Id 14 is equal to "WELTMEISTER" The value in Field Id 27 contains "E5" ------------------------------ Justin Torrence Quickbase Expert, Jaybird Technologies [email protected] https://www.jaybirdtechnologies.com/#community-post ------------------------------Re: Changing Forms
If you're lucky and don't need to show records that use both new and old forms in the same report, you can achieve this simply by changing the form that is used for any individual report. For the rest of us, this solution is not as elegant as I would like, but it is something I have used in the absence of more dynamic form routing features. Note: This solution assumes you have some field in the table that you can use to determine whether the record should use the old version of the form or the new version of the form. Before making any changes, make a copy of the form in its current state. Then, create a new button via the Formula - URL field. The goal of the url will be to direct the user to the same record, but using the old version of the form (the copy that you made). It could look something like this: URLRoot() & "db/" & "?a=er&rid=" & [Record ID#] & "&dfid={ID}" You'll be replacing {ID} with the form id of the duplicate you made. You may also want to make a variant for viewing the record, for that you'll just replace ?a=er with ?a=dr Now, it is time to make the changes you were planning. When you are finished put a section at the top of the page that says something attention grabbing to the user, like "Warning! Use the old form for this record.". In this section you can place your buttons and any helpful message to the user you want. You'd want to hide the section using that condition that can tell where to route the form. For you that may be date, so When [Date Created] is before "XX-XX-XXXX" show the Section "Warning! Use...." . ------------------------------ Justin Torrence Quickbase Expert, Jaybird Technologies [email protected] https://www.jaybirdtechnologies.com/#community-post ------------------------------Re: REST API - Get All Apps
@Ricky Pons I don't believe the RESTful API supports that yet, or at least I haven't run into it. API_GrantedDBs might help if you are comfortable using their XML API. Here is a convenient nodejs library, if you are building something through codepages. If you feel strongly about it, I would recommend giving your support in the form of upvotes to this suggestion in their feedback portal (Or create another that is more specific to your needs) ------------------------------ Justin Torrence Quickbase Expert, Jaybird Technologies [email protected] https://www.jaybirdtechnologies.com/#community-post ------------------------------Re: Formula to calculate values - range of quantities
@BuildPro Not sure if you are looking for assistance with this formula, but here is a revised version: IF( [YEARS EMPLOYED] < .75, 0, [YEARS EMPLOYED] > .7501 and [YEARS EMPLOYED] < 3.0, 5, [YEARS EMPLOYED] > 3.01 and [YEARS EMPLOYED] < 8.0, 10, [YEARS EMPLOYED] > 8.01 and [YEARS EMPLOYED] < 10, 15, [YEARS EMPLOYED] > 10.01, 20 ) ------------------------------ Justin Torrence Quickbase Expert, Jaybird Technologies [email protected] https://www.jaybirdtechnologies.com/#community-post ------------------------------
