Dave Reed
My feedback
29 results found
-
1 vote
An error occurred while saving the comment Dave Reed
shared this idea
·
-
4 votesDave Reed
supported this idea
·
-
6 votesDave Reed
supported this idea
·
-
123 votes
An error occurred while saving the comment Dave Reed
commented
Same issue as many people listed in the comments. Our membership levels feel more like payment options instead of membership benefit differences. Every l"benefit" evel we create needs to be replicated for one-time pay, recurring monthly, and soon recurring annual.
We have a related challenge where we need membership invoices to accept partial payments. [This is a different issue, but highlights the challenge of member level proliferation.]Dave Reed
supported this idea
·
-
33 votesDave Reed
supported this idea
·
-
4 votes
An error occurred while saving the comment Dave Reed
commented
I'd add to this request. We have some larger events and use volunteers to run the events. We do not was to make every volunteer an event admin; it is still to much access. Perhaps a "read only" event admin role that allows check-in?
Dave Reed
supported this idea
·
-
1 voteDave Reed
shared this idea
·
-
13 votes
An error occurred while saving the comment Dave Reed
commented
Adding my support for this. I was troubleshooting a membership issue using the details in the email log. I was confused when the email log showed a member's current renewal date instead of the renewal date that was true as of the day the email was sent.
Dave Reed
supported this idea
·
-
4 votesDave Reed
shared this idea
·
-
36 votesDave Reed
supported this idea
·
-
3 votesDave Reed
shared this idea
·
-
13 votesDave Reed
supported this idea
·
-
79 votesDave Reed
supported this idea
·
-
74 votesDave Reed
supported this idea
·
-
16 votesDave Reed
supported this idea
·
-
27 votesDave Reed
supported this idea
·
-
8 votesDave Reed
supported this idea
·
-
28 votes
An error occurred while saving the comment Dave Reed
commented
This would be very helpful to distinguish between payments for different types of member levels or to distinguish between online store or memebr payments.
Dave Reed
supported this idea
·
-
9 votes
An error occurred while saving the comment Dave Reed
commented
This would be very helpful to distinguish between payments for different types of member levels or to distinguish between online store or memebr payments.
Dave Reed
supported this idea
·
-
28 votesDave Reed
supported this idea
·
Good news and bad news... The most recent version of the Non-Admin API documentation now includes documented support for Coupon Code in the /ApplyForMembership API call. Yeah! Even though no one responded to this in the Forum, I stumbled across the update a week ago.
Bad news... it does not work. Everytime I submit the API request now, I get a 400 error with a message of "Discount code invalid". I'm using the same exact format as the original "idea". The same discount code does work if I use it with the /ApplyForRenewal API call.
I've double-checked the discount code, the contact, the membership level. I've run numerous tests with different variations. I believe this is still a BUG that needs to be resolved.