Add an 'End Date' field for attributes.
Currently users who need a function with a start and end date use Constituency Code, meaning we now have hundreds of constituency codes, and are unable to annote these data. By having two dates on attributes, we would be able to manage time dependent data (e.g. the period over which someone belonged to a particular club/activity) PLUS (unlike constituency codes) we'd be able to use the existing Comment field to describe/abnnotate the attribute
e.g:
Category: Clubs & Societies
Description: Rowing Club
(Start) Date: 01/08/48
End Date: 31/07/51
Comments: Fixtures Sec 49/50, Club President 50/51
-
David Smith
- May 4 2012
- Reviewed: Voting Open
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +876
Related ideas
Adding an end date for attributes would let us track things more efficiently than through constituent codes.
I had clicked on, apparently, the wrong comment. My comment was directed to keep RE database open. This idea group here must have been adjacent.
At least keep it open until you move all fields and capabilities to NXT. Every one of your clients has built their records infrastructure based on their unique accounting and CRM needs. Many of the critical fields we have been using for nearly 20 years seem to be determined "unneeded" for the NXT conversion. Hoping that's just because you're still hooking up NXT to the database, but in case you decide NOT to bring over a critical field, please leave the database open!!!
The added convenience of querying by dates the same way constituencies work would be great as well. I'm all for adding an end date field to attributes. Thank you.
This would be very beneficial for our University!!!
A workaround to not having an end date is to add active and inactive choses to your description table. Example: Rowing Club Active vs. Rowing Club Inactive. Use the attribute Comments field to record time frames (2020-2022).
This is an issue with my Church and I hope that it is worked on soon.
This ideas was originally posted in 2012 and would be a huge help for all the reasons already identified by other users. Is this idea currently under consideration?
YES!!
This issues is a continual pain for our organization. We use a work-around but that creates more confusion for our users. Add another date field!!!
I'm in favor of it.
Excellent idea.
100% agree, would be most helpful.
I presume this would be added to a patch update for those of us who are not hosted?
Thanks.
Michelle Geange
Office Manager
Hours of work: Mon - Fri, 7am-2pm, Ph: 09 750 7203
Auckland Rescue Helicopter Trust
http://www.rescuehelicopter.org.nz
YES YES YES.... would it be too much to ask to see when and who updated what attributes or at least the last time the tab was updated?
and maybe a few more characters than 50
You could also add a sub constituency and a comments section in the constituency area just as well. DO BOTH!
Date this request was asked: May 4 2012... better late than never?
This absolutely would be helpful for our boards (we are a large healthcare org with MULTIPLE boards), committees, in-patient dates (again, healthcare...admit AND discharge is really helpful!). Thank you for considering!!
This would be VERY beneficial in removing the issue of too many constituent codes!
Really need this
Much needed
I have been using the REDB since the early 90s and I have always wanted an extra field like the description that I could choose which type of data element, text, Table Value, date, etc. this would be very powerful. If it was just another date field, then not as powerful.