thankQ Help
Sometimes a user may be asked to renew their membership and instead of renewing their Membership they may instead create a duplicate membership instead. To merge these duplicate memberships perform the following steps in thankQ:
| 1. | If you have not already done so, set Lookup Value Membership Admin --> Multiple Memberships Per Person to Always Prevent or Always Warn. This will ensure that any contact marked as a duplicate of an existing contact with more than one membership will automatically have their duplicate membership caught before it is automatically posted into thankQ: |
| 2. | When you run Web Sync and the memberships are pulled into thankQ an error will appear in the EDI (Contact has another Membership) after an attempt to validate the records: |
| 3. | To set this membership as renewed you will need to lookup the original Membership ID. In this example it is WMBR0030830, and so you will need to change the Membership ID being referenced to this ID so that the membership is now pointing to the existing membership that is already in thankQ. This update will need to be performed in the Membership and Membership Relationship tables. You should also increment the Nth Period (i.e if it was 1 then change to 1.1) and change the Status to Renewed. There may be other fields you might need to adjust as well such as the Membership Start/End Period (depending on the difference between the memberships): |
4. Once you have made these changes press Re-Validate to continue:
| 5. | If the Membership was a paid one you will now get an error in the Membership Payment. This is due to the Membership ID being referenced incorrectly in the payment, which did not previously appear as an error and could not be updated as a result. Once the error appears however it can be fixed by referencing the old membership ID in the payment's External Ref: |
 |
6. Once you have made this change press Re-Validate to continue and the record import should complete itself.
| 7. | The latest payment however will not be fully connected to the membership - to resolve this open the newly imported payment and assign it to the imported pledge via the Assign Pledge to Split option: |
 |
8. The membership should now be successfully merged and fully paid for:
