AM Push cmdb adapter issue
Need some information and guidance regarding AM -UCMDB Push Scenario
When we Discovered new Device from CMDB and push to AM then SeAssignmentt value is changes from in stock to in use but it happening at first time.
then i changed the se-assignment value manually in AM from in use to stock and re-run to Ampush adpater integration that doesn't change the se-assignment vallue in AM.
Wondering why ... it happen only once when it discovered ..
also need to understand that if it's OOB feature or need to do the modification to achive the requirment.
Thanks in Advance for your valuable time
Re: AM Push cmdb adapter issue
Consulting with some folks in the AM team, they advise to open an AM support case, as there are several things to check to find the root of this behaviour.
Please let us know if any concerns.