Target record not found in import set table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-18-2022 11:26 AM
I have a customer trying to create cases in ServiceNow. In dev, they are able to do this just fine passing me their ticket number, which I am using as the correlation_id. So, the case creates with their ticket number in the correlation_id field.
In prod, same version of the import set table, same transform map, same user and same roles for the user, it skips with the error: "Target record not found."
So, why would it allow it in dev and not prod? Any ideas?
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-18-2022 11:31 AM
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0819754
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-18-2022 11:59 AM
I saw that article, but the user has the correct roles to read. It seems to be saying, we can't update a case because we cannot find the correlation_id in any existing case.
Ok, that is fine, except the system should create a case in that scenario, and it is rejecting the case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-18-2022 02:50 PM
Can you check the transform map and the unique field defined as coalesce?
Compare with Dev and both are having the same field mapping and Coalesce.
Check the transform map is in active.
Regards,
Suresh.
Suresh.