Found the culprit. The active link INT:ASICHG:ASA:MultipleAssociate_105_SubmitCHGTemplateAssoc in the guide ASI:ASA:MutipleAssociationPush was not pushing the DatasetID variable to the right place, so the Lookup Join form was displaying the production AND staging records. Curiously it was necessary to push this value to the DatasetID field on the CHG:Template Association form. -- Chris Danaceau AttivaSoft Solutions Architect
________________________________ From: Action Request System discussion list(ARSList) on behalf of Chris Danaceau Sent: Mon 5/2/2011 3:08 PM To: arslist@ARSLIST.ORG Subject: Relating multiple CI's to a change template results in production AND discovery datasets ** ITSM 7.6.03 ARS 7.6.03 I have a customer who wants a Change Template for Windows Server patches. The template would include all matching windows servers. When I relate them one at a time things work just fine. When I select more than one to relate, the application creates CHG:Template Association records for the BMC.ASSET dataset AND my staging Dataset. Ran AL and filter logs on this and did not see the second create. Has anyone else run into this? -- Chris Danaceau AttivaSoft Solutions Architect _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
