ContributionsMost RecentMost LikesSolutionsRe: Creating task with a specific due dateOkay, that helps a lot I just wasn't thinking that. Thank you so much! ------------------------------ Xenia Watterson ------------------------------ Re: Creating task with a specific due dateThank you for the response. I'm comfortable finding the specific month it is created, I don't know how to say, if it is this month then the due date is 09-01 for whatever year. I've only ever done it as add however many days to the start date to figure out what the due date will be. ------------------------------ Xenia Watterson ------------------------------ Creating task with a specific due dateWe have certain tasks that get created when new employees are hired. Most have due dates that are calculated a few days after the start date, but we want to add tasks that will be due on September 1 or March 1 based on the start date (so if the Person is hired and task is created in September, October, November, December, January, or February the task will be due March 1. If it is a March, April, May, June, July, or August hire will have a due date of September 1). How would I write my formula to say if this is the start date, then this is the due date? Thank you! ------------------------------ Xenia Watterson ------------------------------ Date range with non-consecutive DatesWe have a table we use for site visits our technicians make to a customer's site. Currently we allow a single visit for all consecutive day visits (so imagine a 3 day visit on Monday - Wednesday), but if there is a gap in visit days (such as the weekend or a scheduled pause for a quality control check) we require a second visit is made for the next set of days. The reason for this is the formula to show the next scheduled date/time (so if the visit starts on Monday, once that day is done the formula will show Tuesday as the next scheduled day until the end of the days/nights indicated on the visit and then the field will go blank). Is there a way to do the next scheduled date/time field with gaps for days that the visits are not scheduled as the gap days are not always on a Saturday/Sunday weekend? ------------------------------ Xenia Watterson ------------------------------ Changing order of conditional drop down selectionWe are trying to build out an inventory database that shows products available and the stores you can buy them at. I understand how to set up Conditional drop downs (Manufacturer limits Make limits Model) but what if you want to be able to search by more than one starting point. So you can see that XXX Company makes 3 types of TVs (36", 55" and 70"). The 36" inch TV can be purchased from Vendor A or Vendor B, the 55" TV is available from Vendor C and Vendor A, and the 70" TV is available from Vendor B and Vendor C. But could you start by selecting Vendor A and seeing that they sell TV and stereo equipment and the TVs they sell are available in 36" or 55". Think using the Filter function on Excel and selecting any column on your spreadsheet and seeing the rows drop down from there.Re: Summary field based upon two many to many relationshipsThanks for responding. Kickoffs aren't the same as Site Visits because a single tech can do multiple Site Visits for a project (so they could save Puppies in Chicago and Detroit and Minneapolis) but they only need one Kickoff per project. I currently have a report link where the related projects match, but that's not being limited by the matching technician, so it will show all the techs that have the Kickoff for the project or all the projects the tech has had a kickoff for. Summary field based upon two many to many relationshipsI have four tables Projects, Kickoffs, Technicians and Site Visits. The relationships between the tables are set up as Projects < Kickoffs > Technicians but also Projects < Site Visits > Technicians. I need to be able to show if the Technician assigned to the Site Visit has had the Kickoff already for this specific Project. I want to know did Sam the Technician get a Kickoff for the Saving Puppies Project (so good to go for all those visits) but she has not had the Kickoff for the Saving Kitties Project (so needs to have the kickoff for these visits). I am sure it is a super easy solution but I'm stumped. I am not sure how to create a summary field that will show on the Site Visit that either the date of the Kickoff for the related Project and related Technician or at minimum that there is one Kickoff record that matches the related Project and related Technician. I would even be happy to have a report link that shows just the one record that matches these two criteria but I can only have it match the related project or related technician. How do I indicate that the technician has had a kickoff for that specific Project when assigned to a Site Visit?Re: Summary field on sibling relationshipsGreat! Thank you. I didn't want to waste a lot of time on building the relationship if it wouldn't work but it sounds like it will be exactly what I need. I appreciate your time.Summary field on sibling relationshipsI am trying to make a sibling relationship on our Work Order table with summary fields from the lower siblings showing like traditional summary fields on the primary sibling table. Sometimes we need to do progressive billing which requires the creation of new Work Orders for Invoicing purposes but they need to be related back to the primary Work Order (where the actual work is being tracked). I have created the relationship where the "parent" will be the Primary WO and all the new Work Orders will be Secondary WO. But I need to create summary fields showing totals and averages of the billing information for the Secondary WO for inclusion on the Primary WO record for reference and also sometimes included in formulas. I try to add these fields on the Master Table side of the relationship details but the newly created field shows on the Details Table side. I am sure this is a limitation of creating a sibling relationship instead of a traditional parent to child, but I don't want the information in the Primary WO being included in the summary fields as I don't want them counting twice when doing formulas for totals (not all Primary - Secondary WO relationships require inclusion of the Secondary totals in the Primary invoice because some customers want to be billed at multiple points during the WO (not rolled into the Primary WO totals) and some customers want a single billing but may get touch-point totals based on phases of the work (rolled into the Primary WO totals) but get a single bill to pay). So I probably talked in circles but hopefully it makes a little bit of sense.Summary field based upon two relationshipsWithin our database, Work Orders (WO) could have more than one Site Visit - so if a Work Order requires visits over multiple days or technicians from different Deployment Partners (DP), each day and each DP will get a different site visit. The WO will then potentially have multiple invoices (if different DP were used). We house our WO, site visits, check Ins/Outs, DP Companies and Technician each on their own table with various relationships to share information from one to the other in look up or summary fields. We have a checkbox field on the Site Visit that is called Cancelled and when checked produces a field that requires you to pick a reason (Tech No Show is one). So we could roll this up to the WO showing how many visits are cancelled because of no show, but we will need it to be specific to each DP, not just a count for all site visits on the WO. Similar to relate to the DP or to the invoice - it will need to show that this is a cancelled site visit for this DP, this invoice, and this WO. For the late check ins, there is a Duration Formula field called Technician Delay to show the difference between the start time for the visit and the actual check in time within the check ins/outs table. Again, we can roll this up to the WO showing how much total time the technicians were late but it would need to be specific to the DP and this invoice. It is possible that within one WO, there could be two DP used, but one or both could have penalty causing issues as documented on their check in or site visit. So currently, the PM has to go to the different tables to check this - was the site visit cancelled from a No Show? was the technician late? - and then carry this over to the Invoice and enter this information manually to justify a penalty. We would like this to automatically appear on the invoice for them to review and track in one place. Is there a way to add to a relationship a summary field that says "Count the number of Cancelled visits when the DP on the visit matches the DP on the invoice and the WO number matches the WO on the invoice". We've considered doing embedded reports that show this information (list all the site visits on the WO with the field to indicate if the visit was cancelled and why and another field to list all the check ins and any check in delay) but again this would require a manual review to see if the DP associated to the visit is the one that cancelled or was late.