Make 'Bulk Upload Temp Passwords' More Usable/User-Friendly

This is an important feature to work for our elementary students. Privacy laws do not allow the school to issue them email addresses, so the established method of "First Time Logging On" from the login screen does not work for them. When I initially saw that Core had this feature, I was happy. After working through my list of 644 students, I was less than happy. Here is what would make this feature really great:

1. Increase the count of records that can be processed in one file.

When I initially exported the user records from Core, I did so in one file. It was "only" 644 users. The file never processed. I split the one file into three and tried again. The file still did not process. I looked for a knowledge base article or some user feedback, and saw that some people said the cap was around 100 records per file. I spilt my three files into 6 files and tried again; still no luck. Finally I split my 644 users into 13 files (average of about 50) and was finally able to get it to process. 50 records is less than half of one grade for us. This low cap makes this process very cumbersome. Increasing this cap to at least 150, would be a start, but I would like to see it even higher.

2. Provide better documentation to the exact record limit.

The note on the upload page says, "Important: If you are experiencing a timeout, try breaking your file into smaller files." What is smaller? Are we talking about KB or number of lines in the CSV?  I wasted a good portion of my morning through trial and error to find the right level. It would be great to post a useful record limit so as to not waste other people's time.

  • Rick Geyer
  • Aug 10 2016
  • Implemented
  • Attach files
  • Janet Wittenberg commented
    September 17, 2018 20:52

    Sorry this idea wasn't updated.  Last year we made performance improvements to Bulk upload temp password so you shouldn't be experiencing these confusing limits this year.

  • Guest commented
    September 09, 2016 01:18

    It would be great if we could upload the passwords and decided whether or not it needed to be changed at next login. Our team has to manually login to each lower school students account with the temp password and then create a password that is unique to that student in Junior Kindergarten through 5th grade that they can remember. It is a ton of work. Any other suggestions welcome. We do not have an LDAP active directory :(

  • Guest commented
    August 12, 2016 14:46

    Do you have an LDAP server? If so, you could consider integrating your directory server with WH. It's a lot of work to set up (and I believe some extra cost), but it means that whatever roles you select (we do faculty/staff and students) can authenticate against your own servers. Then you can script out bulk password setting for students (provided they are user objects in your directory server).

     

    If solving this problem is your only concern, I think the above is overkill. However, if you think you could benefit from having your teachers use their computer login info for WH, it could be worth it.