easy import changes the content of imported data from alphanumeric to numeric
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-14-2024 03:02 AM
I am using easy import to import new configuration item records but the imported data is not exactly as per the source import template. Specifically alpha numeric values in one column of the source data are changed to numbers when imported to ServiceNow. What I am doing is:
1. Download an import table from the target table list (network gear / cmdb_ci_netgear table)
2.Added data to the import template
3.On ServiceNow selected import type 'Insert'
3.Uploaded the template file to ServiceNow
4.Click upload
5.Previewed the imported data.
6.When previewed i can see that a value of BAR2888AP001 on the import template has been changed to a numeric value of 2,888,001 in the ServiceNow CI form.
On the import template the source data cell is formatted as "Text" and the target field on the CI form is a String field. The target field is the 'Name' field on the network gear form (cmdb_ci_netgear.name) .
The issue is only affecting data imported to the 'Name' field . Other alphanumeric values on the import template are maintained as alphanumeric when imported to the CI form.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-14-2024 04:07 AM
I just did exactly the same on my instance and it worked as expected. Name is filled with BAR2888AP001.
Where did you get this data from? Did you copy/paste it in, or did you, like I did, type it on the sheet. Because with copy/pasting, you could be adding different formats to your sheet.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-14-2024 04:44 AM
Hi, thanks so much for the suggestion, I have tried both ways - cutting and pasting and 'manually' typing in but get the same issue using both methods. I used a "fresh" import template when i manually typed the data in just to make sure i wasnt carrying any issues over from the 'cut and pasted' template . Its so odd