Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies replies
    2
  • Answers answers
    2
  • Subscribers subscribers
    177
  • Views views
    290
  • Users 0 members are here
Related
Options

UCMDB pushing double entry in Service Now

Prasanna Karmarkar

Dear Expert,

we have uCMDB to ServiceNow integration through which we are pushing Business Application CI Type from UCMDB to Service.

In query we limit only 1 CI to push from UCMDB to Service now staging table, but after running integration job we observe 2 records got created in ServiceNow.

we want to know what causing this issue.

UCMDB version 2023.05

Thanks

Prasanna

  • Suggested Answer

    0  

    Hello,

    There is a higher probability to be an issue on SNOW side than on UCMDB. Have you double checked that indeed that CI did not exist in SNOW before.

    To double check on UCMDB side you can

    1.  double check the tql and its layout in order to have all required attributes by SNOW
    2. double check that the test CI does not exist in SNOW
    3. enabled debug for fcmdb*logs on both server and probe
      1. you should see only 1 CI calculated on server side and sent to probe
      2. on probe side you should see the CI being sent to SNOW and its confirmation. Only one call should be logged

    If everything looks good then you could also enable debug on SNOW side to see what happens with the CI.

    Hope it helps.

    Best Regards,

  • Suggested Answer

    0 in reply to   

    ..Also do check in Service Now mapping if a coalesce key is present. You may have duplicates in case of no such key defined.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.