It would be helpful if during the user import process if data for the custom user profile fields could also be imported along with the user.

I would add custom1, custom2, etc. to the list of fields or alternatively custom_shortname1, custom_shortname2. I think this should go after autosubscribe and before the course information.

It would seem simpler to implement custom1, custom2 as you could just use the id number; however, from a user's perspective it may be more helpful to use the shortname.

This came up when a user was inquiring about importing date of birth information for the 3rd party birthday block. If they were able to use custom_dob then we would need to lookup the id value for the custom user field.

– the current list of optional fields includes:
idnumber, icq, phone1, phone2, address, url, description, mailformat, maildisplay, htmleditor, autosubscribe, course1, course2, course3, course4, course5, group1, group2, group3, group4, group5, type1, type2, type3, type4, type5, role1, role2, role3, role4, role5

Let me know if there are any questions. If I get a chance I will go in and see if I can develop a patch file that would get this working. I consider it a low priority; however, I could see its usefulness if admins are making use of the custom user profile fields. Peace - Anthony