When ADDM synchronizes the data to the CMDB, the data is created in the BMC.ADDM dataset (i think). The data is then reconciled between this dataset and your golden dataset (BMC.ASSET).
The Priority value on the base element form has a default value of 5. I don't think ADDM actually populates this value and its probably defaulted when the record is created based on the field value on base element during the synch. Changing the default to Priority_3 should resolve this issue. Make sure you do this from the class manager. Also take a look at precedence groups for reconciliation. This will allow you to define if a particular attribute should retain the value in the BMC.Asset dataset and not be overwritten by the BMC.ADDM dataset value during reconciliation. Hope this helps. Saby ________________________________ From: Joe H. Smith <hornetlo...@gmail.com> To: arslist@ARSLIST.ORG Sent: Friday, October 26, 2012 11:31 AM Subject: ADDM pushing priority field to the CMDB Currently, ADDM is pushing Priority_5 in the Priority attribute for Computer_Systems. We’s like to change that to a higher priority. For instance, Priority_3. We have never edited this or anything, so I assume it’s an OOB value ADDM is pushing. So the questions are: 1. How does ADDM push that priority value. I don’t see it on a host in ADDM 2. How do we change that value that is pushed. I have verified on another system that ADDM does indeed populate the Priority field there also. Thanks _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
