Customize how Member ID is generated
Is there a way I can designation a "starting number" for the member ID field? For example, if I am setting up a new membership database and I would like our member ID numbers to begin at 500.
Just to revived this thread Dmitry
I think all we want is a custom field. The club can define the starting ID, but it auto-increments by 1 when a new contact is added for our members. Then Wild Apricot keeps the user ID but we can have our customer member_ID without having to maintain manually.
I cannot see on any custom fields the option for us to set an auto increment.
I could have written this exact request! Many organizations have their own membership numbers accrued over a long period of time of operation. For us it is 47 years, and our older members do not want to change numbers. Right now, I have to manually assign number for new members who join, which takes a lot of time. Databases can easily incorporate the concept of incremental numbers - Wild Apricot already does this with it's own membership numbers. Why can't we have a field that will help the organizations that use Wild Apricot?
No. You can create the field, but it will not be automatically updated. This is why we still have this in Wishlist
Dmitriy, this is interesting. We have the same question as above - we would like to have a custom "Membership Number" field and have it auto-increment. Are you saying this is possible?
Our organization also must issue a unique membership number to all new members. Plus, we use that number to track when people have joined. While the Wild Apricot member number might help somewhat, many on our board are used to our sequential numbering. Having a numbering sequence in which there are gaps, and having to work with six digits rather than our current low four-digits, would create some discomfort. Lastly, our secretary receives all new membership applications by mail and approves only membership applications - he uses the sequential numbers as a double-check to match membership revenue to bank deposits. I realize that this might be difficult to implement, but it would be helpful. Not at the top of our list of wants, but it would be helpful.
Phil Dailey commented
We have a similar issue in that our constitution requires that membership IDs are generated after a new membership application has been accepted by at least two of the board members. Therefore the system member id cannot be used since it will be generated at the initial application for membership.
We are new clients of Wild Apricot and were expecting to totally convert our current MS Access database to Wild Apricot to improve the flexibility of our membership management. Due to this issue we are being forced into maintaining the MS Access database just to comply with our membership ID rules.
In current version of Wild Apricot you can create a custom field to keep your old membership numbers and then use our system member id field for all existing and new members from now on. Can you comment on this setup vs. your suggestion?
I would add a vote for some kind of customization available for the auto-assigned memberid number.
In our case, we would like to autoassign random six-digit numbers, for example, since we use the memberid code as membership numbers, which are used as keycodes to access one of our facilities. For this reason it is great that the memberid number is unique to a given member, but some members have a 6-digit code, some have a 7.
It would be great if we could control the member ID. It seems really random.
It would be easier if we could track it by entering what number we would like to start with etc.
For November members we would start 1109XXXX
For December members we would start 1209XXXX
Currently we have to assign these numbers manually as a field after the fact, the member ID is pretty useless as is..
Sorry for the delay in my responding.
In our case we have not been using a member ID for our membership (yet), but over the past year have had a growing need for one and will probably start assigning one to each member. For now, I will have to do this myself as the admin when I "approve" applications. Our situation is unique - our membership is based around an annual charity bicycle ride for fallen law enforcement officers. Our membership has grown to the point where our medical staff can't possibly know every member and so they need us to start using member ID numbers so that if, god forbid, we have several riders taken out in an accident they can quickly identify everyone involved and cross-reference our medical records. We have 7 chapters around the country and the medical staff would like to be able to designate a range of numbers for each chapter so they can better track who belongs with who. I can maintain this numbering system myself, but it would be nice if I could set up a field that would automate it as applications are accepted.
Thanks for the quick reply, perhaps you could consider this for a future release.
No further reply necessary.
There is no way to ensure uniqueness of custom field value now, sorry.
I have created a nickname field in my WA db - how can I ensure this will be like the member ID in so much as every members nickname will be unique.
Is there a particular field name I need to use?
yes, ignore memberif for import, it will be added automatically.
userid - yes you can add as custom field.
ok - I think I see the difference -
member id - system record number - auto generated
. . . so is there any reason for the user to ever see this or know about this?
user id - selected by user, as long as it is unique
. . . can be used in place of email for signing in, so that more than one person can sign in with the same email address
QUESTION, as I will be loading a new database in as soon as friendly url's are available -
when I set up the database fields for upload, do I ignire the member id? does it just generate itself as it creates each record? (And go ahead and load the user ids as a custom field for future use?)
I think you are talking about ad-hoc username/userid and this is different from a numeric auto-assigned memberID.
Isn't there another active thread on this topic?
Can't find it right quick, but seems to me the discussion on the other thread was that a system generated "member id" might be better called a "record number" and let the member ID be things that make sense to the organization - or that might already be in place in existing systems
For example, my "member id" in our existing system is "gypse" - it can not be duplicated within the system - has to be unique for that field - but is "user friendly"
Ghostbuster Apricot commented
Could you elaborate what is actual reason to have a well controlled Member ID?
Are you going to use it for some member grouping?
Or may be to get an idea who has registered earlier or later?
We understand your point and we will consider it for future enhancements.