HannahWright2
Qrew Trainee
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Opening Form to Specific Tab
Thank you for your response Brad! 1. I have a landing page table which contains a landing page record specific to each user. When the user follows the link I provide them they have 4 forms they fill out. This landing page is the parent record to the 4 different tables that house the individual forms. So the user will click the "add Form One" button on the landing page which will take them to create a new Form One record in the Form One table. When they save they are brought back to the landing page so they can click the "add" buttons for the other 3 forms. So in short, this method will only be used on the landing page which is a record that already exists. There would not be a situation where they would be adding a record. 2. The users would be accessing this landing page where I am trying to use this method in one of two ways. Either using the link I send to them which is a direct record link or when saving a child record which will direct them back to the landing page. In my testing I was successfully able to get your strategy of using a button to trigger the code page to run and move me to the specific tab but when I try to use that same code page with the image onload technique it won't run. Here's my current code when trying to use iol instead of a hyperlink: var text iol = "<img qbu='module' src='/i/clear2x2.gif' onload="javascript:if(typeof QBU=='undefined'){QBU={};$.getScript(gReqAppDBID+'?a=dbpage&pagename="; var text /iol = "&rand='+new Date().getTime())};">"; $iol & "specifictab.js" & $/iol Code Page: specifictab.js var nextTabLink=$("li.ui-tabs-selected").next("[style!='display:none']").children("a"); $("#saveAndKeepWorkingMenuOption").click(); var noErrorDialog=$('#qbDialog').length==0; if( noErrorDialog ){ $("#tab_t3_link a").click(); location.assign('#navTop'); }; ------------------------------ Hannah Wright ------------------------------Re: Conditional Record Pickers in Grid Edit
Hi Marissa, About a week ago I might have had the same/ a similar error. I do think it's a bug that QB needs to fix. I had my field that filters the record picker options as a formula field and had another drop down field that could override the formula field. This allowed me to automatically filter if I was creating a record through the form by using the related state but if I was creating a record using grid edit it would not be related yet to anything so I needed this override field. It gave me all kinds of issues because it wanted the formula field which was the field that filtered the record picker options listed first and then my override state drop down field and then my record picker field. I'm not exactly a fan of how that ended up looking since essentially the first column isn't editable and the second column is where the user would actually need to select the state. It was just too clunky. Hopefully my experience is some use to you! ------------------------------ Hannah Wright ------------------------------Quick Base Fomula to find Mode of an Array
Hi there, I'm trying to figure out how I can determine the mode of an array of numbers using a Quick Base formula. From what I've found, Quick Base has formulas for finding the mean, and median but not the mode. I was considering using javascript in one of my formula fields but have very minimal javascript exposure. Does anyone know how I would find the mode natively or in javascript using a Quick Base formula field? Any help is greatly appreciated! ------------------------------ Hannah Wright ------------------------------Formula URL - View Record Without Record ID#
We have recently discovered that creating a report link to view a record on another app will create a relationship between those two apps. We have a complex system so we would like to avoid app to app relationships. It is for this reason we are moving toward iframes for this type of functionality. With this in mind, is there any way to create a link to view a specific record (not a report) without having that records Record ID#? In other words, can you use a field other than the Record ID# in the url to view a record? I appreciate any feedback! ------------------------------ Hannah Wright ------------------------------Re: Using a Jinja Boolean Expression in Query Step of Pipeline
Hi Mark, For my specific purposes that would not have worked. Criteria don't have to be specific sometimes they could accept "ALL". For example: Job: RN vs Job: ALL One criteria might only apply to RN's but another criteria might apply to any job we place for. This specific or ALL scenario is one that applies to all of the different criteria types I would need to query for. This being said, I would not be able to create a formula field that listed all the possible ways a criteria could match a person and use that in the pipeline. I've attached a picture of the Query I mapped out before writing the Jinja. It was also important I know why a criteria matched the query which using Jinja in Pipelines allowed me to do since I could comment out the scenario that pipelines ran on. -Hannah Wright ------------------------------ Hannah Wright ------------------------------Re: Juiced EFP Addon Subtable Formatting
I have found that same issue. It seems that if the ~strid=xx~ is located under a line it will be interpreted as a paragraph break. If it's located on the same line then it will be like shift+enter. This has solved my spacing issues. shift +enter example formatting: Work History ~strid=xx~ would be formatted on the generated document like this: Work History ~strid=xx~ ---- Alternatively, Work History ~strid=xx~ would be formatted on the generated document like this: Work History ~strid=xx~ If you want to see more examples of what I'm talking about let me know and I can upload examples when I get home tonight. Hope this solves the issue you're dealing with too! ------------------------------ Hannah Wright ------------------------------Re: Using a Jinja Boolean Expression in Query Step of Pipeline
Mark, I appreciate your feedback on this. Your strategy was certainly going to be my plan B if I could not resolve how to use the new Pipelines functionality. I opened a ticket with Quick Base and was able to meet with a member of the Pipelines Development team to discuss Jinja syntax and how to use it in this way. He did mention they were aiming to come out with more in-depth Quick Base specific documentation in the next two weeks. They also plan on adding access to a Jinja formula library much like they do for regular formula fields while editing your code. The major thing I needed to change in my strategy is that you cannot reference the fields you are querying in Jinja on the query step. You need to query for everything and then have a conditional statement based on all of the records queried. From there you can now use the Expression Boolean fields like I was wanting to. I do suggest splitting your Jinja into many different Expression Boolean fields if you're working on something similar to this because it gives you the ability to troubleshoot if your query isn't giving you the results you were expecting. I also needed to make a few adjustments to my syntax. Based on his feedback I have been able to successfully implement this design using Pipelines and Jinja. Using Jinja has allowed me to comment out the many different ways a record could match criteria. I hope this helps someone out there looking to do something similar! ------------------------------ Hannah Wright ------------------------------Using a Jinja Boolean Expression in Query Step of Pipeline
I have a table full of criteria and every time I create a new record in a different table I want to query to see what criteria the new record matches. I have 5 different fields that will be compared against the criteria which can be organized in many different ways. While it is possible for me to put in several different filters I feel it would be better to maintain if I were able to comment out things and edit the code. For this reason, I am trying to use Jinja as a boolean expression in the query step to see if fields on the new record match fields on the criteria (queried table) which will then allow the pipeline to continue. So my question is, is there a way for me to compare a field from the trigger step (new record created) to a field on the criteria table? I know with the low code query format it allows you to pull values from the trigger step over to the fields you want to change. So far I have manually been adding b.field_name into my code and wanted to make sure me manually referencing the table I'm querying in jinja is part of the functionality Quickbase has designed for. A huge thank you to anyone who can help! ------------------------------ Hannah Wright ------------------------------
