I’ve created jobs to migrate data directly to the corresponding AST:XXXXX forms, as well. The workflow in those forms also creates a ReconID in the SANDBOX record which causes the merge function to create duplicate records in ASSET unless we clear them out before hand.
All that our staging form is doing is checking the model information via our Product Catalog and then moving the data to the appropriate AST form based on CIType. This way we don’t have to break data feeds down by class. The only thing I can think of to get around this is to duplicate the attribute fields on the BaseElement form so the data will show up regardless of whether we clear out the ReconID. Anyone see any issues with doing that? Patrick Swint | Tractor Supply Company CMDB System Analyst P:615-440-4240 F:615-484-4240 [email protected]<mailto:[email protected]> From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Roger Justice Sent: Tuesday, February 04, 2014 2:52 PM To: [email protected]<mailto:[email protected]> Subject: Re: Reconciliation Jobs and AST:Attributes Form ** The recomendation since I was working on CMDB 1.1 was to always import the data through the CMDB or AST join forms since the workflow is already there to push the data to the proper regular form Base Element and Computer Sys tem as an example and set the Instance ID to be the same on both of the entries. with 8.0 a non CMDB form was added AST:Attributes that is only used when the Asset Join is used for import. -----Original Message----- From: Patrick Swint <[email protected]<mailto:[email protected]>> To: arslist <[email protected]<mailto:[email protected]>> Sent: Tue, Feb 4, 2014 3:39 pm Subject: Reconciliation Jobs and AST:Attributes Form ** We are running into a catch-22 style situation with some of our reconciliation jobs for a 8.1 migration. The data that we have in our existing environment is made up of hardware info in a BMC class (e.g. BMC_ComputerSystem) and financial information in the AST:Attributes class. We have a Pentaho job that moves data to a staging form where workflow kicks off and moves the data to the appropriate forms and links the forms together using the InstanceID and ReconciliationID. The problem occurs when we attempt to reconcile this data from our SANDBOX dataset to our ASSET dataset. If we run a standard identify and merge job, the merge creates duplicate entries in ASSET…I’m assuming this is because our workflow creates a ReconciliationID as part of the form linkage so the identification fails against existing data from ADDM in the ASSET dataset due to the different ReconciliationIDs. I can zero out the ReconciliationIDs for the record in BMC_BaseElement and AST:Attributes and the reconciliation job then identifies and merges successfully…but any data from AST:Attributes. I’ve tried using custom identification rule sets for each class in our SANDBOX and run into the same issue as with the standard job. I also lose Attribute info if I leave the ReconID in AST:Attribute alone and only zero out the one in BMC_BaseElement. Questions: a) Is there an easier way to import data that shows up in a join form, e.g. AST:ComputerSystem? Keep in mind that we’ll need to do this for several different asset classes. b) If not, are their recommendations for changes to the data import workflow or in the reconciliation job? Is there a different way to link data on these forms?? How are the rest of the folks on here managing this process? Patrick Swint _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
