ContributionsMost RecentMost LikesSolutionsRe: Thinning the Multi-Select Text choice poolWell, in a sense the assigned extensions are already connected. They are setup as part of unique numbers on a phone number table. The phone numbers connect, via summaries, passed up through related tables. From the phone number table to a Service Detail table, and finally to the support case table and to the form the HR contact is using to put in the new hire request. Ultimately I would have preferred a drop-down select method, but in the past I have not had much success in trying to do similar filtering operations (The service detail table is what ties together the Phone Numbers, the support case, and the Extension pools) ------------------------------ Douglas | dhines@tritonnet.com | Service Delivery Coordinator | Tier II Support | Systems ------------------------------ Thinning the Multi-Select Text choice poolI've seen similar posts on the boards, but not one worded quite like this... : Is it possible to utilize several MST fields to thin out an available options in a "master" formula-MST? Imagine the following scenario... A small "New Hire" app is requested by HR to easily initiate a mountain-sized pile of tasks to be done by filling out a few fields in a form and pressing save, but can't be bothered to keep a list of active company extensions anywhere. The app is to be fed a list of company contacts from another table. The HR rep wants to only be able to select available available internal company extensions to avoid having to reprint Business Cards. Master MST pool : {401-449} Department Summary Pools: Billing: {410-429} Sales: {401-409} Repair: {430-439} Already-assigned Extensions include : 409, 412, 431, 433, 402, 413, 417, 404, 401 Our derived summary Pools then look like this: sales_pool : 401,404,402,409 billing_pool : 412,413,417 repair_pool : 431, 433 Is there a native method to remove the items in the summary pools from the master MST? I already plan to break up the comparison based on their departments (for less computing). What can I do natively to accomplish a list of selectable, extensions still available in the repair pool? ------------------------------ Doug Hines | dhines@tritonnet.com Learning it As I Go | Tier II Support | Systems ------------------------------ Re: Filtering Related Parent based on values in Child table fieldsThere is not. They are directly related to each other. ------------------------------ Douglas | dhines@tritonnet.com | Service Delivery Coordinator | Tier II Support | Systems ------------------------------ Re: Formula to get a value of a field from a record that is one month older than another recordCould you possibly utilize a summary field in the Client Snapshot table? Set the summary to get the total value of spending (assuming you have that in a field somewhere), where the creation date of the snapshot is 30 days in the past. Then you could add a report formula field to calculate the difference between this newly added field with the snapshot data already in the system. ------------------------------ Douglas | dhines@tritonnet.com | Service Delivery Coordinator | Tier II Support | Systems ------------------------------ Filtering Related Parent based on values in Child table fieldsThe subject may sound similar, but I've not come across something like this in the forums yet. Maybe it's not possible and I just haven't joined the bandwagon yet. Imagine, if you will, a table of [Orders] with multiple One-To-Many Relationships with a [Contacts Table] (for those not imagining..) ------------|[Related Contact1] ------------|[Related Contact2] [Order] -|[Related Contact3] ------------|[Related Contact4] ------------|[Related Main PoC] As not-imagined above, the user can choose up to 4 Contacts for this order form. I'm trying filter the giant list from the Contact table (via the[Related Main PoC]) by passing it through some sort of filter that would match the four previously selected contacts. I've tried a few things, each with worse results than the last, including pulling apart the different fields I might need, then reassembling them to be used in a formula text field; used as the target of a Dropdown Selection field... only to find that said selection field recursively added all the formula field values from all the orders as an option; instead of the values solely given in the Formula Field of the given order, The reason I've added yet another Relationship to my Contacts table is to try and avoid breaking any working systems we have in place now. I'm hoping that the answer is glaring obvious to someone(s); and I'm just oblivious. However I fear that I'm asking Quickbase to do something it cant. ------------------------------ Doug ------------------------------ Re: Welcome to the Community Introduce Yourself Here!Hi there, My name's Doug and it's been just over five years since I was given the task of rebuilding our customer, service, and contact database when the server it was running on had a irrecoverable hard drive failure. Since then I've built, rebuilt, patched, and tweaked our current database app to the wonderful conglomeration it is today. 1) My biggest challenge has been finding time to make much needed improvements to the visual style, layout, and automation the my company's flow requires. My next hurdle has been updating my outdated html/js scripting methods and figure out which new languages to adopt. 2) My desired instant-master skill is kind of broad: digital art. 2D or 3D. From fantasy matte paintings done in Photoshop to sculpting hyper-real characters and environments in ZBrush. I'd like to be able to express what I see in my head accurately to other people. 3) While I don't think I've mastered anything (besides maybe the search tool), I am definitely exploring all aspects of QuickBase. I'd like to be able to build a single interface for my coworkers to use that access and utilizes all our different vendor APIs and portals without opening a dozen different web browser tabs to accomplish the task. ------------------------------ Douglas Service Delivery Coordinator | Tier 2 Support | Systems and Sales dhines@tritonnet.com | ------------------------------ Re: Another jQuery help request...back to basics..Yes, the &praram method looks familiar.. I like familiar. I'll mess around with this weekend and see if I can't make some headway. Thank you. Re: Another jQuery help request...back to basics..I've moved to the code page route. I have a html file that I can successfully call from a formula URL on one of my tables. I am now running into a road block of being able to pass/store field values so I can use them in the code page. I'm currently attempting to use a sessionStore, but I think the conversion into quickbase scripting is throwing me for a loop. Is sessionStoring of parameters a smart way to pass this data?Re: Another jQuery help request...back to basics..Sorry for the long wait in the reply. I don't have access to work email on the weekend. To answer everyone's questions : Yes. The end goal is two fold : to populate a mass of Telephone numbers and decrease the time/clicks my coworkers perform adding the records. However, would rather not have accidents occur, which is entirely possible with the import function (I'm assuming you're speaking of the "import data from a file" option) The best case scenario would be that they're all in sequence. Unfortunately there are often times we will have a few missing phone numbers that breaks a block of numbers into multiple blocks. On the flip side, we also have instances where there are absolutely no numbers in sequence. (I handle those personally via the import method). The solution I am attempting to create would be for those instances of sequenced numbers. My coworkers would simply need to enter the first telephone number and last telephone number, and the script would handle the procedural stuff and error checking. Re: Another jQuery help request...back to basics..To answer Chayce's question, the phone numbers come from data that we get from our customers and have to manually enter at this time. (We're in telecom). We deal with thousands of phone numbers per account. Our current method of entry for a range of phone numbers starting at 111-111-1111 and ending at 111-112-9999 is to make a series list in Excel, then slowly but surely copy and paste special into our editable table. Since Quickbase by default only shows 4 or 5 extra rows in this mode, we can only increase the number of records 4 at a time... over the span of many many phone numbers.