Dale and Meg DeJager

My feedback

  1. 131 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    71 comments  ·  Wishlist » Members  ·  Flag idea as inappropriate…  ·  Admin →

    We have started analysis for this issue, and it seems that key problem is how Wild Apricot handles level changes close to renewal date. The system is currently designed to collect the full new level amount and set renewal date according to new level renewal policy. All prepaid amounts for old levels are disposed. Moreover, since no prorating occurs, the new level might be effective only for a few days.

    As a first step, we suggest to redesign how level change is working and add prorating there:

    - Level would be changed immediately, as now - Remaining portion of old membership level payment will be applied to new level - For new levels with specific renewal date (e.g. annual levels with renewals Jan 1st) apply the pro-rating settings for new applications: - Allow member to pay only a pro-rated amount of the new level fee (e.g. six months before renewal…
    An error occurred while saving the comment
    Dale and Meg DeJager commented  · 

    All of our membership levels renew/expire on the first of the year. We also need this feature. Right now if a member is paid up to next year and they change their membership level and pay for the new level, the renewal date is not changed. This is bad. What is desired is for the renewal date to be advanced as it is when a member renews. We have to find these records and do it manually now.

  2. 470 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    210 comments  ·  Wishlist » Emails  ·  Flag idea as inappropriate…  ·  Admin →
    Team Husky responded

    Sorry for the late update.

    The first step was finished and emails can now be carbon copied to contact’s alternative emails. To do so the contact fields which store the alternative emails must be explicitly marked on the email setting page.

    Unsubscribing will unsubscribe all alternative emails simultaneously because they all belong to the very same account. The person clicking “unsubscribe” is warned about this on the unsubscribe page.

    For now we paused the development of this feature. but not for good. :) So I’m changing this wish status back to “collecting comments”.

    Thank you everyone for a valuable feedback.

    An error occurred while saving the comment
    Dale and Meg DeJager commented  · 

    Excellent. Do you have a description of how this feature will work? Will the user be able to login with either email address, or will one still be "primary" for the account?

    Dale and Meg DeJager supported this idea  · 
  3. 12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Wishlist » Import / Export  ·  Flag idea as inappropriate…  ·  Admin →
  4. 61 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Wishlist » Members  ·  Flag idea as inappropriate…  ·  Admin →
    Dale and Meg DeJager supported this idea  · 
  5. 23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Wishlist » Members  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Dale and Meg DeJager commented  · 

    I fully agree. The documentation actually suggests assigning the bundle member to a different non-bundle membership type, but this is not appropriate if there are no applicable levels. The only solution that I've been able to come up with is to assign them to a non-bundle level and then mark them as lapsed. Also ugly. I suspect the issue is that if they are just made into a regular contact any membership history will be lost, but if they are just a member because they are in a bundle, such history really isn't important to me. If you really wanted to keep history, just add a note to the notes field when you unbundle them and make them a contact in the same way that a note is added when a membership is renewed.

    Dale and Meg DeJager supported this idea  · 
  6. 295 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    70 comments  ·  Wishlist » Events  ·  Flag idea as inappropriate…  ·  Admin →
  7. 11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Wishlist » Online payments  ·  Flag idea as inappropriate…  ·  Admin →
    Dale and Meg DeJager shared this idea  · 
  8. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Wishlist » Members  ·  Flag idea as inappropriate…  ·  Admin →
    Dale and Meg DeJager shared this idea  · 
  9. 31 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    17 comments  ·  Wishlist » Finances  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Dale and Meg DeJager commented  · 

    We also are very interested in importing donations. We have a history of multiple years of donations in our Access database. Even the WA API does not allow donation importing, only payments. Our requirements are fairly straightforward. Ideally we would import a spreadsheet of donations. One column would contain the existing WA ID. Additional columns would match up with the system fields for donations and the user defined custom donation fields. We would be satisfied with importing only new donations and having you auto-number them as they are imported.

    I suspect one thing that must be thought about is the possibility that someone imports a bunch of donations and then realize that they made some type of mistake and need to delete them. It would be nice for this and many other reasons to be able to delete all donations that were imported in a particular import.

    Dale and Meg DeJager supported this idea  · 

Feedback and Knowledge Base