Form requirement nuanced trade-offs with proper relational structures
I have two related questions! Someone suggested using grid edit reports on my forms for a more all-in-one parent-child editable comprehensive form. That's not working at least on my end -- has anyone had grid reports be available within a form? I'm reorganizing another section of my app for a division that hasn't moved over to my current setup yet. In their legacy setup, there is currently a one-form-fits-all, which requires many things based upon the service level they rendered. We're moving to a "Clients", "Cases", and "Service Calls" -- which means I no longer can require things at the Client or Case level based upon the extent of the service call..... is this just a trade off I have to make? I'm concerned people might not go back into the parent record and update with additional information as it's received in this new setup (and hence why the grid edit would honestly be a fabulous option -- bring the Service Call record right onto the master record and edit it all from there).28Views0likes1CommentStrange Problem with a relationship and record picker.
I have a long standing table, Core Returns, that has a lot (too much, but just blame Admins long retired) of information. There is a field that gets filled in at a point well after the record is created, automatically, through updates. That part is working fine. I recently added another table, HVNE PO's, as part of a different project that does share some data with the older table. There is a reference to an 'Equipment' number. That number is the Primary key in the HVNE PO's table. I have it set where the HVNE PO's table is the parent table and Core Returns is the child table as that same equipment number can and does crop up in the Core Returns table multiple times. The Equipment number, however, does not necessarily exist in both places. The Goal is to allow a User to look from the Core Returns table and see if that Equipment number exists over in the HVNE PO's table. The users' decision about what to do next is impacted by this. So that's what I want. My Relationship is like this: HVNE PO's is Parent, Core Returns is Child. Equipment is the Text (Key Field) in HVNE PO's. Ret_Equipment is the Text (Reference). The reports display everything as expected. Now, in the form to look at records in the Core Return, when just looking, it displays as expected, but when you go to Edit the record, Ret_Equipment displays a date and gives a drop down with completely unrelated information. If I don't touch that field, make other changes that I need to make, when I return to the report or the eyeball view, it's fine. The problem is that I may occasionally need to edit that field and now it's all screwed up for that workflow. I have a gut feeling that it is a simple setting somewhere, but for the life of me I can't find it.43Views0likes3CommentsGetting an index value from a record
Assuming I have a way to do survey by pushing a button which does a count with a timestamp. I want to get the records list by their attempt time which might be in their chronological order of attempt. The max I do attempt is 3. I understand I can use summary field to get the first and last attempt using the Minimum and Maximum but now the value in the middle is what am struggling to get. Anyone with an idea how to go about it? I will appreciate.Solved91Views0likes7CommentsData Migration
Since QuickBase is making new RecordID how do i go about migrating into the RecordID used by QuickBase instead of relying on PersonID and OrderID/PersonID of the old database where the exports are coming from? I have some ideas that i can export the main customer table after inporting into QB and get the RecordID there and then future exports can have the RecordID added to them before importing. Can I override the default RecordID or something like that? What is the best way to go about importing from another database? Export From: Table (client) - PersonID Table (orders) - PersonID one to many Import to QuickBase: Table (Client) - receives a new Record ID made by QuickBase. Table (Orders) - receives a new RecordID made by QuickBase relationship joined to RecordID in client as one to manySolved83Views0likes6CommentsRelationship mastery (hidden performance killer)
As a Quickbase builder managing a growing application, I want to understand how relationships impact system performance so that I can design my data model in a way that stays fast, scalable, and easy to maintain as complexity increases.54Views0likes4CommentsLookup & add multiple records from a child table and add them to a parent table record
Hello Quickbase community! I'm stuck on trying to build a configuration where I can lookup & add multiple records from a child table, and add them to a parent table record. I have a primary table, Films, full of Film records. I used to have tags/labels for these records that I kept in a multi-select text field, but I now have more than 100 values, so I needed to create a related table. So, I created a new table, Categories. What I'd like to do is be able to add multiple Category records to one Film. I was able to figure out how to add 1 Category to each Film, but I wanted to be able to add 2 or more. In my screenshot, my Film record, 'Spider-Man: Brand New Day', has the Category record 'Franchises' attached to it. I also need to add the Category records 'Spider-Man', 'Actor | Tom Holland', and 'Actor | Zendaya' to the Film record. Shouldn't I be able to click a button (based on a Formula URL field) to add records one by one, which will then display in a mini table of related records? Thanks in advance!Solved36Views0likes2CommentsSecurity Group Management
I am working on a new application which will act as our recruiting/employee management system but will not be an HRS platform. This application will handle all the activities that occur before they become an employee. In our IT environment we use security groups to help provision employees into groups that grant them access to data, programs, digital locations, etc. These security groups are rule based and are used to examine an employee's Company, Department, Job Title, and Office Location to determine their group membership. I'm trying to build an interface in QB which would display to the user the various security groups the employee will be placed in based on the selections made in the fields referenced above. An employee will be in at least 1 group but could be in multiple groups and we currently have about 175 different groups configured. I considered creating a single formula field in the Employees table, called Security Group, which would hold all the various security group rule formulas, but that felt a bit too much to manage. I also considered creating individual formula fields, 1 for each security group, but that too feels too much to manage. I have also considered creating a Security Groups table which has 1 row for each group. The table would include: Group Name, Group Type, Group Description, and Group Rule. The group rule field would hold the actual QB formula that could be used to evaluate if an employee fits into that group. But I'm at a loss as to how to connect the Security Group table with the Employees table so that Employees can benefit from the group rule formulas it holds. Again, an employee can be in 1 or more security group. Looking for any suggestions on the best way to set this up so that the management of the security groups is nominal (we may need to create more in the future), so that we can see which security groups an employee would be a member of, and so we could see all the members of each of the security groups.118Views0likes5CommentsMany to Many Relationships
I'm trying to do this the easiest way possible and could use some advise. I have 4 tables Market, Activites,Base Agreements, Admendments The activities table can be related to one or more of each of the other tables but don't have to be related to all of the other tables. I was hoping that I could for example in the Activities table have a field named Market and it be a multi select field. Then on the Market form, I could show all of the Activities that have that market selected. I don't know how to filter that report to only show the activity records that have the market name. I appreciate any assistance.Solved99Views0likes2CommentsTracking Most Recent Data
Good day everyone! This is likely convoluted. I haven't been able to figure a way to actually do this and I feel like I'm missing something obvious. I have a couple of tables that will hold some information. The tables involved: Asset Table Affected Asset Ticket Asset The asset table hosts the information of the Asset itself (Serial Number etc). We create a new record in the Affected Asset table based off the information in the Asset table that attaches ticket information to it. I'm trying to add information to the affected Asset Table that when we create that record, it will record what's wrong with that asset and why we are getting it back. What I want to do is. When we go to add the Asset onto an OOW Ticket, that it populates the Ticket Asset Report with the Latest "laptop Issue" field based off the Assets Serial Number (unique identifier). I am unsure how to grab the most up to date. I likely skipped a step by cutting out the Asset Table in general? I made the Affected Asset field called Laptop Issue, connected it to Ticket assets and created a Field called Up to Date Laptop Issue, but the formula the AI keeps giving me doesn't seem to work. Would the better work around be to have the Asset Table record itself populated the latest Affected Asset Laptop Issue and go from there? Or is there another, easier way that I'm missing entirely.Solved65Views0likes1Comment