Hi J.T.
Unfortunately, I'm not sure if there is a way around that if you are using the Data Management Tool (DMT). I used Patch 9003, but I think 9005 is the same in this regard. I my case, we had a total of 60 support users across 48 support groups to import, with slightly varying application permissions. This required defining 34 templates to handle that. In another case, we had 80 support users across 100 support groups, with many unique app permission requirements to import. After doing the math on how many people templates that would require, we decided to bring them in with just the basics (IM, Task Users, Etc.), and then let them adjust the specifics from with Remedy. I'll be watching this thread to see if someone has figured out a way around that. Leonard _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of J.T. Shyman Sent: Tuesday, August 05, 2008 12:49 PM To: [email protected] Subject: Data Management Application (Patch 9005) - Concepts All, I'm currently working with the new ITSM Data Management suite and have run into a conceptual issue that I thought I saw discussed on here before but I can't seem to find the right search terms to unearth it. The former data load process, the foundation data load, had two spreadsheets that specified application permissions (i.e. Incident User, Asset viewer, etc..) and support group memberships for specific users. The new data management suite goes a different route and uses templates instead. Thus, a given set of application permissions and group memberships are attached to a template and that template is used to create a user. This is all well and good when you have a "simple" environment in which, for example, there are a limited number of application permission combinations (i.e. everyone is going to get one of three "sets" of permissions) and everyone belongs to a limited number of support groups. But what if an environment is more complicated? What if, for example, there are about 75 support users. Of these 75, about 50 could be classified into two application permissions groups (either IM Floating or IM/PM/CM Fixed) but the rest are all unique combinations of permissions. To make it more complex, each user belongs to one or more groups and there are many possible combinations. Unless I am completely misunderstanding how this is designed this would necessitate the creation of a separate template for each application permission/support group combination and then a template would have to be used to create the user with that combination. Other than creating a few generic templates and doing the rest by hand, assuming the above is correct, is there a more efficient manner in which to import this information? Thanks! --- J.T. Shyman __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
