CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions (Moderator: Dave Greenberg) »
  • CiviMember Usability Issues: Import Improvements & Date Functions
Pages: [1]

Author Topic: CiviMember Usability Issues: Import Improvements & Date Functions  (Read 1538 times)

CiviTeacher.com

  • I live on this forum
  • *****
  • Posts: 1282
  • Karma: 118
    • CiviTeacher
  • CiviCRM version: 3.4 - 4.5
  • CMS version: Drupal 6&7, Wordpress
  • MySQL version: 5.1 - 5.5
  • PHP version: 5.2 - 5.4
CiviMember Usability Issues: Import Improvements & Date Functions
July 08, 2008, 07:35:52 pm
Hi have to suggestions/complaints for CiviMember.

1) During the import process, CiviMember is very picky about the difference between 01 and 1.   For instance, dates reading 1/1/2008 will not be accepted or understood by CiviCRM.  On the other hand 01/01/2008 will be understood.  This is very inconvenient, especially when Microsoft Excel 2003 is a common format many of my clients store their data in, and 01/01/2008 is not a valid date formatting option.  (Go ahead, L33t h@x()rz, rant about Bill G, fine, but it's what a lot of people use, that's just a fact).

2) When entering a membership manually (through Find Contacts), the "Join Date" provides an earliest date of 1988 in the drop down menu.  I find it slightly silly that CiviCRM assumes that no organization that might use CiviCRM would have a member that has been around since before 1988.  Many charities have people (lifetime members, major donors, etc) that have been around since the 70s, 60s and before!

Please let me know if these two things can be added to the next cycle.  Thank you.
« Last Edit: July 08, 2008, 07:44:42 pm by Stoob »
Try CiviTeacher: the online video tutorial CiviCRM learning library.

speleo

  • Ask me questions
  • ****
  • Posts: 396
  • Karma: 28
  • CiviCRM version: 4.3.1
  • CMS version: J! 2.5,9
  • MySQL version: 5.1
  • PHP version: 5.3.24
Re: CiviMember Usability Issues: Import Improvements & Date Functions
July 09, 2008, 02:56:24 am
Totally agree with point 1.

For you second point check CiviCRM  » Administer CiviCRM  » Global Settings » Settings - Date » Advanced Date Input Settings (you'll see this last option in the Date Input Fields panel).

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: CiviMember Usability Issues: Import Improvements & Date Functions
July 09, 2008, 10:30:15 am
Quote from: Stoob on July 08, 2008, 07:35:52 pm
1) During the import process, CiviMember is very picky about the difference between 01 and 1.   For instance, dates reading 1/1/2008 will not be accepted or understood by CiviCRM.  On the other hand 01/01/2008 will be understood.  This is very inconvenient, especially when Microsoft Excel 2003 is a common format many of my clients store their data in, and 01/01/2008 is not a valid date formatting option.  (Go ahead, L33t h@x()rz, rant about Bill G, fine, but it's what a lot of people use, that's just a fact).

Please file an issue in the issue tracker for this and we'll look at handling the "trimmed" date format when we refactor the Import code (probably for release 2.2). thx!
Protect your investment in CiviCRM by  becoming a Member!

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions (Moderator: Dave Greenberg) »
  • CiviMember Usability Issues: Import Improvements & Date Functions

This forum was archived on 2017-11-26.