ContributionsMost RecentMost LikesSolutionsRe: Why Won't Add New Record show in record picker?I submitted a help ticket referencing this conversation. Thank you both!Re: Why Won't Add New Record show in record picker?I'm the administrator and none of the 'hide' check marks are active. So I'm still confused on this. Any other thoughts?Re: Why Won't Add New Record show in record picker?I'm not familiar with a 'sync/connected' table. Is this the same as a 'related' table? Would you be able to elaborate?Weighted Average Calculation & Recursion IssueI have two tables: 1. Properties (parent); and, 2. Buildings (child). I want to have a gross rental income data entry field in the Properties table that populates each Building's portion of rental income based on a weighted average of square footage. Unfortunately, using summary fields that then lookup down to Buildings results in what QuickBase has called "recursion" that does not allow totaling of gross rents, so I cannot then total the different rent types in the Buildings record, or other totals. Is there a work around to this? Conceptually, this is what I'm trying to achieve: Properties Table: [Gross Residential Rent Income] (dat & [Gross Commercial Rent Income] Buildings Table: [Gross Building Residential Rent Income (Summary Field Lookup from Properties)]* ([Building X Square Footage] / [Gross Building Square Footage (Summary Field Lookup from Properties)])= [Building X Residential Rent Income] Currently returning a 'recursion' error (see screenshot with QuickBase help) Repeat for 'Commercial Rent', then... [Building X Residential Rent Income]+ [Building X Commercial Rent Income]= [Building X Total Rent Income] From here... Properties Table: [Buildings Total Rent Income (Summary Lookup) Why Won't Add New Record show in record picker?A record picker won't show the Add New Record button. I've checked user roles, and the parent record's advanced settings, and the form's report link settings to no avail. See screen shot below of missing button. Help? Record Picker Shows Record ID#, not Reference Proxy in Grid EditWhen I go to edit a Proxy Reference field in Grid Edit, it only shows the Record ID, though I've changed the Record Picker options in the parent record's Advanced Settings. Two screen shots below: Parent Record advanced settings for Record Picker; and, Grid Edit view from the child record showing the oddity. This is somewhat related to an issue in another conversation, but not quite the same: https://community.quickbase.com/quickbase/topics/does-record-picker-not-work-in-the-grid-view Re: does record picker not work in the grid view?Related to this, when I go to edit a Proxy Reference field in Grid Edit, it only shows the Record ID, though I've changed the Record Picker options in the parent record's Advanced Settings. Two screen shots below: Parent Record advanced settings for Record Picker; and, Grid Edit view from the child record showing the oddity. Re: Relating Parent Record to Child Records Across Applications So... this issue has confused me after some serious blueprinting of options and limitations in Quickbase. I had setup another conversation and just posted much more detail on the issue:https://community.quickbase.com/quickbase/topics/using-formulas-actions-or-other-means-to-auto-relat... I created diagrams (see comments inthe other conversation)of each scenario I could think of which might get me closer to the goal but without adding significant workload/data/relationship management. Re: Using Formulas, Actions or Other Means to Auto-relate Records or Facilitate Field Changes The issue I have is that no relationship arrangements fully satisfy what we're attempting to achieve. Current scenarios I've attempted or researched: Option A: Create Resources (Parent)-Properties (Child)relationship limits only one resource a la one-to-many. We have two or three resources per property which would need to be a parent. Option B: Create a field or category(ies) in the Properties tables on which to filter related child records (e.g., Incidents) when reporting. This would require manual changes should the Resources and Assignments records change. Too much data management. Also, use of formulas to automate is not feasible from the research I've done (e.g., cannot use across tables upstream). Option C: Scrap the Properties-Incidents relationship and/or addan Property Assignments(Parent)-Incidents(Child) relationship. This would require too much management of data for the multiple Property Assignments. Option D: Create new Staff Regions Tables. They would be related: Properties(Child)-Staff Regions(Parent to Properties/Child to Resources)-Resources(Parent). This requires additional data management. E.g: if a Property Assignment changes, the Staff Regions table(s) would also have to be updated (duplicative). Option E: Similar to "D", create Staff Regions table as a parent to Properties, child to Property Assignments. This makes a circular relationship (is this a problem?): -Properties(Parent to Property Assignments/Child to Staff Regions) -Staff Regions(Parent to Properties/Child to Property Assignments -Property Assignments(Parent to Staff Regions/Child to Properties) Option F: Replace Property Assignments table with a table for eachAssignment (e.g., Accountant, Property Manager etc.). Searching assignments by property is hindered by this setup, and would only be visible in the Properties table. Option G: Reverse the relationship of Properties and Assignments. Not possible given the one-to-many nature of the relationship. Below is the best I could come up with brainstorming and thinking through each scenario! Using Formulas, Actions or Other Means to Auto-relate Records or Facilitate Field Changes Wracking my brain... I have a "Resources" table, and a "Properties" table. They have a many-to-many intermediary table "Resource Assignments" (child to both) which relates "Resources" and "Properties". I have a third table that is "Incidents" (child) related to "Properties". See diagram for clarity on the end goal. I have been wracking my brain trying to solve how to minimize relationship/data maintenance byrelating "Resources" to"Incidents"(or adding an auto-filled field as filter). 1. I can't relate Resources-Incidents (employees come and go) 2. I can't relate Resources-Properties (increased relationship management, and it's be nicer to report on any Resource's Incidents as child to Properties) Questions/Brainstorming: -Is it possible to use a formula across tables or applications to achieve some automation? -Is it possible to use Actions to achieve this? -Could I create a new parent table to Properties and Resources that could auto-fill set fields on which reporting filtering could be achieved?