Yes, I did follow the instructions (silly me!). All of the records appear to be imported, but most of them are without the correct status value. Any idea how I recover from where I am? Rick _____
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of White, Ed Sent: Wednesday, May 09, 2007 6:58 AM To: arslist@ARSLIST.ORG Subject: Re: DSL console not displaying data ** RIck, I don't know if you followed the instructions where you only tried to do one import at a time. If you did that will not work. There is a KB that says that you actually have to click all the boxes on the import console and start the import. This will take about 5 hours, but it does get the job done. Hopes this helps. Ed White Senior Systems Consultant The Ohio State University Medical Center 640 Ackerman Road PO Box 183111 Columbus, Ohio 43218-3111 (614) 293-2089 (phone) [EMAIL PROTECTED] _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Tuesday, May 08, 2007 5:03 PM To: arslist@ARSLIST.ORG Subject: DSL console not displaying data ** I selected the option to import the DSL data when I installed Problem Management, and just got done going through the steps on the PDL:ESIDImportConsole form to update the attributes of the DSL records. If I do a search of the individual PDL:ESID forms, there are many records there (up to about 80K), but the DSL console will not display any records at all, even with a global search. The tree table field on the DSL console pullls data from the PDL:ProductDictionaryPatch form, and there are ZERO records returned from a global search against that join form. I verified that the user I am logged in as has DSL Master and Viewer access, as well as Config Categorization Admin. What should I do to refresh this data? Is it safe to just delete and re-import the records? Would it do any good if I did? If so, the KB says that there are Import mappings in the application install directories, but I've done several searches for .arm files, and there aren't ANY. I'm thinking that's at least a documentation bug at this point. ITSM 7.0.2 patch 3 Rick Cook __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
