Import Set warning logs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2024 09:28 PM
We have a transform map for sccm to fetch and map the collection members with two field maps both being coalesce, one is Device and another one called collection with choice action as "reject". The import set table is pulling lot of records. below are the field map script for both. This transforms map is generating import logs called "More than one target records exists for target table u_m2m_sccm_collection_member with query u_cmdb_sccm_collection=716327938798123"
Collection:field map script
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2024 10:37 PM
Hi @Rashmi Rao ,
Check why duplicates are occurring in your import set table.
Ensure your import set table has unique keys to prevent duplicates.
Review your import process for errors that might create duplicates.
Add error handling to your scripts to avoid unnecessary logging.
Mark it as helpful and solution proposed if it serves your purpose.
Thanks,
Anand
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2024 10:47 PM
The issue you're facing is due to the coalesce fields in your transform map. When you have more than one coalesce field, ServiceNow checks for a match on all coalesce fields. If it finds more than one match, it generates the log message you're seeing. Here are some steps to resolve this issue:
1. **Review Coalesce Fields**: Check if both coalesce fields are necessary. If not, remove the unnecessary one.
2. **Check for Duplicate Records**: As you mentioned, duplicate import set rows could be causing this issue. You can create a script to identify and delete these duplicates.
3. **Modify the Transform Script**: You can modify the transform script to handle multiple matches. For example, you can add a condition to only return the most recent match.
4. **Use a Unique Identifier**: If possible, use a unique identifier as a coalesce field to avoid multiple matches.
5. **Limit the Number of Logs**: You can limit the number of logs generated by modifying the log level in System Logs > Properties.
6. **Clean Up Old Logs**: Regularly clean up old logs to prevent them from taking up too much space.
7. **Optimize the Transform Map**: Review the transform map and optimize it to improve performance and reduce the number of logs generated.
8. **Use Scheduled Jobs**: Schedule the import set to run during off-peak hours to reduce the impact on system performance.
Remember, it's important to thoroughly test any changes in a sub-production instance before applying them to your production instance.
nowKB.com
For asking ServiceNow-related questions try this :
For a better and more optimistic result, please visit this website. It uses a Chat Generative Pre-Trained Transformer ( GPT ) technology for solving ServiceNow-related issues.
Link - https://nowgpt.ai/
For the ServiceNow Certified System Administrator exams try this :
https://www.udemy.com/course/servicenow-csa-admin-certification-exam-2023/?couponCode=NOW-DEVELOPER
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2024 11:41 PM
Why Ai ? @Rajdeep Ganguly
☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....