creating duplicate change in bidirectional integration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2025 05:43 AM
When I choose the assignment group during the initial change creation process, it creates two changes one at a time. I have used ebonding change integration 2 servicenow with bidirectional. There would be a change in the integration if I hadn't chosen the assignment group at first. Help us solve this problem, please.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2025 05:45 AM
Please help me to fix this issue
Please check this updates
- Ebonding Service Account
Field changes•
2025-01-16 03:05:12
- Correlation displayCHG0039637wasCHG0039636
- OA
Ebonding Service Account
Field changes•
2025-01-16 03:05:11
- Correlation displayCHG0039636 Like this
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-04-2025 11:03 PM
Hi @Anandkumar g ,
Hope you are doing well.
If you are open to explore dedicated integration solutions for syncing changes and other entities between 2 servicenow instances, I would recommend you to try out a fully decentralized solution Exalate.
It provides you an access to it's groovy based scripting interface with ready to go templates and also a lot of documentation for syncing system/custom fields very easily.
We do offer a 30 day free trial incase you want to evaluate the product.
Thanks, Dhiren