EmmaFinger1
Qrew Trainee
Joined 4 years ago
User Profile
User Widgets
Contributions
Re: Rank using a query
Thank you @Quick Base Junkie I did test the option you posted and it also works, but as you said, the solution from @Mark Shnier (Your Quickbase Coach) is cleaner and will probably be easier to maintain when I undoubtedly get asked to add more fields to the calculation. ------------------------------ Emma Finger ------------------------------43Views0likes0CommentsRe: Rank using a query
Thank you @Mark Shnier (Your Quickbase Coach) I did end up using your solution and added a field that changed the format of the date field and appended the build priority to the end of it with a dash. If(IsNull([Expected Start Date])=false,(ToFormattedText([Expected Start Date],"YYYYMMDD")& "-" & [Build Priority]), IsNull([Expected Start Date])=true,(ToFormattedText([Final Date Required],"YYYYMMDD")& "-" & [Build Priority])) I then used the new field in a formula to "rank" the records using the ranking option shared by @Quick Base Junkie in her blog post, which allows me to use the record ID as the differentiator when 2 records are otherwise the same (a tie), in the ranking. var text QZER = "{289.EX.'true'}AND{58.EX.'"&[Region]&"'}AND{45.EX.'"&[Data Center Name]&"'}AND{291.LT.'"&[For Build Order Combined]&"'}"; var text QONE = "{289.EX.'true'}AND{58.EX.'"&[Region]&"'}AND{45.EX.'"&[Data Center Name]&"'}AND{291.EX.'"&[For Build Order Combined]&"'}AND{10.LTE.'"&[Record ID]&"'}"; Size(GetRecords($QZER))+Size(GetRecords($QONE)) ------------------------------ Emma Finger ------------------------------21Views0likes0CommentsRe: Rank using a query
Thank you for the suggestion Mark, I should have specified that only 3 of the 4 fields are date fields. The Build priority is a numerical ranking 1, 2, 3. I believe what you are suggesting would only work if all 4 of the fields are date fields, but perhaps I can append the build priority to the end of the date fields to still make this work. I will give that a try. ------------------------------ Emma Finger ------------------------------73Views0likes2CommentsRank using a query
Hi everyone, I have a list of records that I need to rank, first by the expected start date, then by the final date required, then by the build priority, and last using the record ID. One thing to note is that the expected start date field is usually blank. This is the formula I am using currently, and it is working with the exception that if a record has the expected start date populated then it numbers those and then starts the numbering over again on the records that do not have a date entered in the expected start date. For example if 2 of my records have an expected start date they would be ranked 1 & 2, then the next record (without an expected start date but with the earliest final date required) would again be ranked 1. I have referenced Quickbase Junkies videos which is how I got this far. Any help/suggestions would be appreciated. var text QZER = "{289.EX.'true'}AND{58.EX.'"&[Region]&"'}AND{45.EX.'"&[Data Center Name]&"'}AND{148.BF.'"&[Expected Start Date]&"'}"; var text QONE = "{289.EX.'true'}AND{58.EX.'"&[Region]&"'}AND{45.EX.'"&[Data Center Name]&"'}AND{148.EX.'"&[Expected Start Date]&"'}AND{129.BF.'"&[Final Date Required]&"'}"; var text QTWO = "{289.EX.'true'}AND{58.EX.'"&[Region]&"'}AND{45.EX.'"&[Data Center Name]&"'}AND{148.EX.'"&[Expected Start Date]&"'}AND{129.EX.'"&[Final Date Required]&"'}AND{47.LT.'"&[Build Priority]&"'}"; var text QTHR = "{289.EX.'true'}AND{58.EX.'"&[Region]&"'}AND{45.EX.'"&[Data Center Name]&"'}AND{148.EX.'"&[Expected Start Date]&"'}AND{129.EX.'"&[Final Date Required]&"'}AND{47.EX.'"&[Build Priority]&"'}AND{10.LTE.'"&[Record ID]&"'}"; Size(GetRecords($QZER))+Size(GetRecords($QONE))+Size(GetRecords($QTWO))+Size(GetRecords($QTHR)) ------------------------------ Emma Finger ------------------------------Re: Limit the number of records returned in Pipeline using a field value
Hello Mark, Yes, the limit field will only except 2 characters and if you try to enter anything besides a number it displays a warning and will not allow it. ------------------------------ Emma Finger ------------------------------34Views0likes4CommentsLimit the number of records returned in Pipeline using a field value
Does anyone know how to limit the number of records returned in a pipeline quickbase channel records search using the value in another field as the criteria? I know that we can hard set the limit using the limit field in the step, but I need the ability for it to depend on the value in a field. ------------------------------ Emma Finger ------------------------------46Views0likes6Comments
Groups
Women's Qrew
For builders who identify as women to connect and learn from each other.15 Posts
