You haven't spotted any entity relationship diagrams out there for the data tables in ITSM 7.6, have you???
Don and I are trying to figure out all of the tables (in order) that he will have to move data for - from our production ARS 7.1.00.002 / ITSM 7.0.03.009 system to the new ARS 7.5.00.004 / ITSM 7.6 system - using rrrchive, import, Migrator, carrier pigeon; whatever. Anything that ties to other tables on record ID, like everything that uses Group IDs (including Incidents, etc.) has to come over exactly as it is on the 7.1/7.0 system or those relationships will not be maintained; you cannot use the Data Management tool or the load tables since they generate a completely new set of record ids. Our concern is that we don't know about all of the underlying association tables that store those relationships, and were hoping that there are ERDs out there that document them. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Guillaume Rheault Sent: Tuesday, February 23, 2010 10:23 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM7.5 Data Management Tool--Specifically, Load Wizard ** Hi Don, I only use the spreadsheets in the ITSM Data Management tool for reference. What I do is actually import the data in the "load" forms with the import tool. To figure out what are the "load" forms, in DevStudio, list the forms whose name contains "load". I got 110 "load' forms in ITSM 7.5.1. For instance, the load form for CTM:People is CTM:LoadPeople Guillaume ________________________________ From: Action Request System discussion list(ARSList) [arsl...@arslist.org] on behalf of McClure, Don [don.mccl...@unt.edu] Sent: Thursday, January 28, 2010 4:07 PM To: arslist@ARSLIST.ORG Subject: ITSM7.5 Data Management Tool--Specifically, Load Wizard ** I encountered the following situations utilizing the ITSM7.5 Data Management Utility. For those who have not yet encountered this 'wonderful' inventory item: First, installation: initial Windows 7 installation with default locations resulted in structure being under c:\Program Files(x86) on this Win7/x64 platform. Unfortunately, said structure is read-only, and did not respond to administrative change to write-eligible. Installation into c:\Users to access user space still encountered issues with writing CVS files from Excel macros, as Windows 7 security is very finicky concerning allowing macros to execute at all, let alone write files. Environment was re-installed on an XP machine, where these characteristics are no longer a hindrance. Second, filenames: this installer named the Macro files under the various sub-versions as: (workbook)CSV without a three-letter extension. System will not recognize them as Excel files at all without renaming them to : (workbook)CSV.xls (and, yes, the *CSV capitalized is hard-coded into batch files to find them for execution). Third, location sensitivity: please remember that the installation directory is hard-coded into worksheets by the installer at install time, so moving this structure (or copying from one platform to another...) requires significant attention and name-modification. Fourth, running the data import from User 7.5 : The 'convert CSV' and 'import CSV' functions each call a popup which prompts user to search for: location of DataImport.exe, location of Excel.exe, and installation directory for the overall data management structure. Yes, these will be searched the first time, as defaults noted by the Windows client are probably incorrect. CAUTION: these two popups expect DIRECTORIES--but the actual Windows search which is invoked will not allow a person to stop on a directory, requiring a standard file. Therefore, the easiest way was to selected a file WITHIN each desired directory. Then the user simply erases the filename (ONLY!) from its data window, leaving the first-level parent directory which is what the two functions require for their respective windows! Oh yes--this Data Management tool must be executed from the User Tool. Seems like a really appropriate place for the BMC development team to implement MidTier capability, right? After all, the statement of direction is that the Windows Client is headed for oblivion. I am interested in other user experiences on this item--either directly or to the list! Don W. McClure, P.E. Applications Administrator,CITC Call Tracking Administration University of North Texas dwmac @ unt . edu _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
