BradElmore
8 years agoQrew Assistant Captain
Is it possible to leverage a report link field to create a relationship
I have two tables: Table A (Customers) and Table B(Memberships). Table A is the Parent Table to Table B (child).
Customer may have multiple Membership records. On the Customer record form I have 2 views that display related memberships
1st View) Direct Relationships - Displays memberships that are related to the Customer via the Related Customer field.
2nd View) Indirect Relationships (possible relationships) - Displays memberships that are related via -- Report Link field -- based on Customer Table [City] and Membership Table [City]
The 2nd view is used to help identify additional Memberships -- that should be in the 1st View (Direct Relationship).
Is it possible to have a "button" field that appears within the 2nd View....So that when an app user identifies --- a membership -- that should be Direct ---- can click this "button" -- within the 2nd View (which is a report Link/View) -- so that a direct relationship is created -- populating the Related Customer field within the membership table -- with the Customer key id?
Thanks for any advice.
Customer may have multiple Membership records. On the Customer record form I have 2 views that display related memberships
1st View) Direct Relationships - Displays memberships that are related to the Customer via the Related Customer field.
2nd View) Indirect Relationships (possible relationships) - Displays memberships that are related via -- Report Link field -- based on Customer Table [City] and Membership Table [City]
The 2nd view is used to help identify additional Memberships -- that should be in the 1st View (Direct Relationship).
Is it possible to have a "button" field that appears within the 2nd View....So that when an app user identifies --- a membership -- that should be Direct ---- can click this "button" -- within the 2nd View (which is a report Link/View) -- so that a direct relationship is created -- populating the Related Customer field within the membership table -- with the Customer key id?
Thanks for any advice.