Skip to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Pulling merge data in from other tables - need help!

Featured Replies

Hi all,

 

I have an email template table where users of my solution can create data driven email templates which used to pull data simply from the same table.

 

My problem now is that the data is in a separate table and there are multiple records to pull data from as merge fields.

 

I'm pulling data from a contacts table where a few of the related contacts are flagged as 'primary' contacts.

 

I want to pull in merge variables but get filemaker to identify the primary contact records and pull data from those only, or from the first primary contact in the sort order.

 

Attached is a screenshot of my merge variable calc using the substitute function to replace the merge text...

 

At the moment this just pulls in the first or second contact's first and last name field, i need it to look at the related contacts and pull in data from primary contacts only

 

Does anyone have any idea how you could best do this?

 

post-102321-0-87848600-1397747426_thumb.

Usually I insert the ContactID of the primary contact right within your Company (?) table.  

 

Then if you have a Contacts value list, based upon ContactID and showing second field of the concatenated full name, and use pop-up menu, you can place it anywhere and have the name show without requiring relationships throughout.  But for merge field, either then pull the value through your relationship (we would need to see your graph and know the table occurrence name of the layout you are on) or create a calculation in your Company (?) table to hold its primary contact name.   

 

Passing values through the relationship is preferred over adding another calculation but we need to understand your structure here before recommending further.  :-)

  • Author

Hello LaRetta, thanks for your response!

 

The contacts table is linked to the email correspondence table through a join table to my Events table, then the email table (where this merge variable 'substitute' function lives).

 

There's no direct relationship between Contacts and Email, so i can see the related Contacts from email but not sure how best to to make this work.

 

If you could explain in simpler terms I'd appreciate!... how should i insert the Contact ID of the primary contact right in my Events table?

 

thankyou for your help. :)


Would creating a direct relationship between contacts and a new instance of the email table make things easier to filter using the relationship?

 

The contacts table is linked to the email correspondence table through a join table to my Events table, then the email table (where this merge variable 'substitute' function lives).

 

Would creating a direct relationship between contacts and a new instance of the email table make things easier to filter using the relationship?

 

I don't know because I still do not know how you are related.  Please attach screen shot of your graph showing the connections for this piece or better, create a simple file showing just the pieces being discussed.

  • Author

Ok, will post a graph tommorow, thanks for your help!

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.