I did exactly the same thing, only from Version 5.0 to 6.0. I spent hours of time doing detailed mapping, especially since we had customized multiple dropdown menus on the Asset form as well. To manage those, I built new fields on the old form to hold the values on the new form for Status type fields, then modified records to reflect what old value would be in new form, then exported, then imported using the 'new' status value I had updated on the 'old' form....whew....is that confusing or what? I also didn't understand how to work with the underlying structure so it took me a lot of time to get all the underlying forms and values updated correctly, then to rebuild our custom fields from scratch. Our users aren't happy either - same issues - it seems like I spend a great deal more time doing 'training' to help them understand how to get what they want. But, the good news is, we got ALL our data over intact, so I guess in the end it was successful. I too am hoping that next upgrade will not be quite so painful. :) Candace
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Pierson, Shawn Sent: Tuesday, August 22, 2006 11:49 AM To: [email protected] Subject: Re: HelpDesk 6.x - CMDB I upgraded to Asset 6.0 from a really old version (I believe 4-something) and use the CMDB, but it was a major adjustment. The users were not happy with the new complexity in the system because they can't just open a form and get all assets in it if they want. It took some time to adjust. Also, because my data was so old, it was not possible to simply upgrade asset. I ended up exporting everything to CSVs, and on my development system I created some test assets of each of the types I was going to import to and made sure that I had the same fields filled out the same way in relation to the classid and other system generated fields. Also I did end up customizing Asset 6.0 and CMDB 1.0 because there are fields that someone added in the old system that did not exist and were fairly important. I'm hoping to do it a little more cleanly in the future and be able to store things like rack locations in the proper table instead of adding a field to BMC_ComputerSystem. Additionally, because the Asset system is harder to navigate and much harder to enter data into, you will really want a discovery suite like BMC provides. Cheers, Shawn Pierson -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Sanford, Claire Sent: Tuesday, August 22, 2006 1:39 PM To: [email protected] Subject: HelpDesk 6.x - CMDB Are any of you out there using the Help Desk package and struggling with the way they have changed the Asset Tracking part of the package to the CMDB? What did you do to work around it or to use your old data in the new format??? We track 4 major things. PC Scanner Monitor Printer We don't need all of the other fluff and stuff. ARS 6.3 HD 6.0 Oracle Win2003 Thank you! Claire ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org The information in this e-mail, and any files transmitted with it, is intended for the exclusive use of the recipient(s) to which it is addressed and may contain confidential, proprietary or privileged information. If you are not an intended recipient, you have received this transmission in error and any use, review, dissemination, distribution, printing or copying of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately of the erroneous transmission by reply e-mail, immediately delete this e-mail and all electronic copies of it from your system and destroy any hard copies of it that you may have made. Thank you. ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org ----------------------------------------- ***************************** This message contains information from Silicon Valley Bank, or from one of its affiliates, that may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify the sender immediately by telephone or by replying to this transmission. This message may include indicative rate information relating to one or more products offered through Silicon Valley Bank, or affiliated broker-dealer, SVB Securities. Rates and yields shown are provided for informational purposes only, are not guaranteed, and are subject to market conditions and availability. Nothing in this communication shall constitute a solicitation or recommendation to buy or sell a particular security. Columbia Cash Reserves, Columbia Treasury Reserves, Columbia Institutional Cash Reserves, SVB Securities Liquid Reserves, SVB Securities Institutional Liquid Reserves and SVB Securities Horizon Shares are offered through SVB Securities, a registered broker- dealer and non-bank affiliate of Silicon Valley Bank. Investments in these products require the involvement of a licensed representative of SVB Securities. Investment products offered through SVB Securities are not insured by the FDIC or any other Federal Government Agency, are not deposits of or guaranteed by Silicon Valley Bank or its affiliates, and may lose value. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
