Answers.Body: <p>You may find this provides the missing feature you need</p>
  
  <p><a href="https://civicrm.org/extensions/nzcofuzioncivitoken" rel="nofollow noreferrer">https://civicrm.org/extensions/nzcofuzioncivitoken</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-11-14T22:22:15.053Z
Answers.Text: Ah cool. I see you get around the issue of multiple memberships by only using "latest".
Answers.UserDisplayName: Demerit
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-11-15T05:30:11.290Z
Answers.Text: We've tried this, but it doesn't seem to provide up to date data. Plus, we have members with multiple memberships which would confuse this token.
Answers.UserDisplayName: Marcel Klehr
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-11-14T22:18:49.150Z
Answers.LastActivityDate: 2019-11-14T22:18:49.150Z
Answers.UserDisplayName: petednz - fuzion
Answers.Body: <p>I think this is a "context" thing meaning that when you are emailing, even from "Find Memberships", you are emailing to CONTACTS and so are in the contact context, whereas for example if you do a "Find Memberships" and then from the actions menu choose "Print/Merge Document", you are in MEMBERSHIP context and can choose tokens like Membership Fee.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-11-15T05:23:57.857Z
Answers.Text: So, I cannot use membership tokens in emails anymore?
Answers.UserDisplayName: Marcel Klehr
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-11-14T22:20:53.030Z
Answers.LastActivityDate: 2019-11-14T22:20:53.030Z
Answers.UserDisplayName: Demerit
Body: <p>I would like to use the membership.fee token in a mail. However, it isn't displayed in the list of tokens the mailer view offers and it's not working when I use it manually. I saw a suggestion to use a membership context, but I'm not sure what that means exactly. I've tried "Find members", saving the list of contacts to a dynamic group and selecting them as recipients, but this won't work either.</p>
  
  <p>I'm running civicrm 5.18.0</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-11-15T06:53:40.773Z
Comments.Text: have you considered Scheduled Reminders based on Membership entity - may get around the problem
Comments.UserDisplayName: petednz - fuzion
Tags: <civimail><civimember><tokens>
Title: Membership tokens missing after upgrade to civi v5
ThreadText: # Membership tokens missing after upgrade to civi v5
  
  (Asked by: username_0 on 2019-11-14)
  
  I would like to use the membership.fee token in a mail. However, it isn't displayed in the list of tokens the mailer view offers and it's not working when I use it manually. I saw a suggestion to use a membership context, but I'm not sure what that means exactly. I've tried "Find members", saving the list of contacts to a dynamic group and selecting them as recipients, but this won't work either.
  
  I'm running civicrm 5.18.0
  
  **Tags:** civimail, civimember, tokens
  
  > **Comments:**
  > **username_1**: have you considered Scheduled Reminders based on Membership entity - may get around the problem  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2019-11-14. Score: 1
  
  You may find this provides the missing feature you need
  
  <https://civicrm.org/extensions/nzcofuzioncivitoken>
  
  > **Comments:**
  > **username_2**: Ah cool. I see you get around the issue of multiple memberships by only using "latest".  
  > **username_0**: We've tried this, but it doesn't seem to provide up to date data. Plus, we have members with multiple memberships which would confuse this token.  
  
  ---
  
  ### Answer by username_2 on 2019-11-14. Score: 0
  
  I think this is a "context" thing meaning that when you are emailing, even from "Find Memberships", you are emailing to CONTACTS and so are in the contact context, whereas for example if you do a "Find Memberships" and then from the actions menu choose "Print/Merge Document", you are in MEMBERSHIP context and can choose tokens like Membership Fee.
  
  > **Comments:**
  > **username_0**: So, I cannot use membership tokens in emails anymore?  
  
  ---
  
  