Populating Child Table Date Field to Parent Record
I have a Parent/Child table relationship for two tables. On the Child table there is a date field that I would like to populate up to the Parent table for use on every new child record in the Child table. Do I need to create a new one to many relationship for the current child table to the current Parent table flipping them in this new relationship or can this be done in the current relationsip? Thanks Brian
Most Recent Record
I have a parent table called Deliverables that pulls in the Project Name into my child table called Buy Out. In Buy Out, each project has multiple Scopes. Each Scope can have many line items over time, with a Date field that’s filled in by the user. What I want: A Table Report that groups by Project Name → then by Scope. Under each Scope, I only want to display the most recent line item (based on the Date field). So if Project A has Scopes Electrical, Mechanical, and Plumbing, I’d only see the latest record for Electrical, the latest for Mechanical, and the latest for Plumbing. What’s happening now: If I create a Summary field for Maximum Date, it only gives me the most recent record for the whole Project, not per Scope. In a Summary Report, I can see the max dates by Scope, but I can’t get all the other line item details. In a Table Report, I can group and sort so the latest is on top, but I can’t filter it to only show that one row per Scope. What I’m asking: How can I build a Table Report that actually only shows the most recent record for each Scope of each Project?
Permissions - How can I keep my permissions as-is but allow for a specific field to be visible?
Hello, Full context: We have a staff table that all employees have access to, but only to view their own information. We also have a PTO table with a calendar report that the team has access to, but because the permissions for the Staff table is set to "when user is 'User'" they are unable to see any of the related names for the PTO records (PTO table is a child table of Staff table). Is there a way, or formula, to keep the same level of privacy on the Staff table whilst allowing the team to see just the related staff name for the PTO Records? Thanks!
problem populating relationship field from import
In a new QB app we created, we have a table "Phishing Attempts" where we want to create records by importing a spreadsheet. We also have a table "Targeted Users" which has employee info such as Employee ID, email, position, etc. Phishing Attempts table has a relationship with Targeted Users table, where we have the Employee ID field from Targeted Users included in the Phishing Attempts record form along with lookup fields that are automatically pulled from Targeted Users table. The spreadsheet we want to import to create new records in Phishing Attempts table includes an employee ID number. When we import the spreadsheet, we select the target field Employee ID in the Phishing Attempts form. The problem is that the Employee ID field in the Phishing Attempts form is not populating when we do the import. The ID number in the spreadsheet matches exactly what is in Employee ID in Targeted Users table. Is this not working because the Employee ID field in Phishing Attempts is pulling from Targeted Users table? Is there a way to get this to work?Trying to build connected records
Table 1 - Requirements Table 2 - Meetings For each requirement there can be multiple meetings, owned by separate sales rep. I already have these two tables, Now if SalesPerson_A has a Meeting_1 for Requirement_1 then an associated record is created in Table 2 - Meetings, but if the same SalesPerson_A has 5-7 follow up meetings for the same Requirement_1 then 5-7 more separate associates records are created and we have created a field dropdown - Round of meeting where we are manually managing, 1st, 2nd, 3rd, etc to keep track, then we are manually copy pasting the previous meetings links in the coming up meeting to access them. this is too outdated and time taking. Also SalesPerson_B can also have a Meeting_1 for Requirement_1 then another new record is created in Table 2 - Meetings n for further follow ups its same manual way. What i want to achieve is that if SalesPerson_A has a Meeting_1 for Requirement_1 then an associated record is created in Table 2, Called Record 1, then I can have someway to keep all the next rounds of meeting under the same, each meeting is different, we have different agenda, people we are meeting, meeting links to join so for each record here there is a lot of information we need to enter, also various fields about how that meeting went, etc. need to manage this separately for each round. what can be the best way to achieve it. we never know we will 1 only or 7 or 10 meetings for a requirement.
