I have a client that has provided me with an excel file containing 300+ user names they need in Laserfiche as LF Users, not AD users.
Is there a way to import this CSV in the admin console and have it create all these accounts automatically?
I have a client that has provided me with an excel file containing 300+ user names they need in Laserfiche as LF Users, not AD users.
Is there a way to import this CSV in the admin console and have it create all these accounts automatically?
There are a couple ways to do this. The simplest might be to import them in as xml. The admin console allows you to export and import the various elements as xml's. You can create one user with the settings you want and export it from the admin console. Then you can manually add the other users. It's not automatic, but it's likely better than doing 300+ in the UI.
Great thanks. I saw the ability to export as XML, but how would I import it once I've modified it?
Importing is an action you can perform on the category itself. In the desktop administration console there should be an option by right-clicking on the Laserfiche User node itself. The web administration console will have something similar.
Thanks Justin, unfortunately I'm not seeing this in the administration console when I right click on the user node. when I right click and look at all tasks it only has export xml, new custom view, and perform search.
Looks like it's on the repository node itself: http://www.laserfiche.com/support/webhelp/Laserfiche/9.2/en-US/AdminGuide/LFAdmin.htm#Importing_Exporting_a_Metadata_Object.htm. That's what I get for not double-checking the exact location.
Great! Thanks for all the help Justin. I'll give that a shot.
Justin,
That worked in terms of getting the user accounts into the system, however how would I go about setting a default password for all those users we've imported? Would that have to be done directly from SQL? I'm not seeing a trigger in the xml to set the password.
Hrm, yes, that's a good point. It doesn't include password definitions since that's not something you would have access to on export. It looks like you may be able to add the 'temporarypassword' attribute to set one on import though. I haven't tried it myself so it might require some expirimentation.