Hello Folks,
I'm interested in getting a hold of info regarding the best way to load User records from a CSV (comma-delimited Excel text) source.
The short story is that we are implementing a new Remedy system and are looking to populate all tables with predefined data. I've already been successful (I guess) at importing the CTI, Location, People tables from the same type of source. As soon as I get the Groups table done, I will be ready to import my data into the User table.
Now, here's my quandary: I have heard from, I hope, reliable sources that in populating the User table in such manner, it is not unusual to encounter a situation where visibly all seems to be OK (Configuration Mgr show the correct info for an individual, User form shows correct license assignemnts, groups seem to be correctly populated, etc), yet the moment that one of these loaded users logs in to Remedy, they begin experiencing errors concerning lack of license, lack of membership to appropriate groups, etc. As I understand it, the solution is to essentially go into ConfigMgr and litterally recreate the license and group assignments manaually for EACH user.
I would really like to avoid such hassle if I can. Otherwise, I would like to know if I MUST plan on doing these manually anyway.
Please advise if the above is in fact an issue to potentially experience and if there are "tips" to avoid the problems. I would also like hear about a "best practice" approach to doing this (required fields, caveats for pre-during-post import, etc).
Thank you so much.
Jairo Arvizu

Jairo,

is there a reason you can't export the data into an .arx file and use the Remedy Import tool to bring it on to the new server? I've never had issues with licenses/groups doing it that way.

Since you mentioned the Configuration Manager app...you must be using the COTS apps. You must also load the the SHR:Assignment form with appropriate data or your users won't be able to take ticket assignments. Simply adding the group to the users User form entry isn't enough. You will also have to load the "support groups" as opposed to other types of groups into the SHR:ApplicationGroups form.