Unable to find out which all fields got updated post transform

[SNOW46]

Hello All,

We have a requirement to run a reconciliation report between Oracle and ServiceNow for user records to get updated in SNOW. We usually get an excel sheet that contains all the active users' records information including all the fields.

I have tried loading the data in Import Set and performing the field mapping using Mapping Assist and running the transform on the sys_user table. I can see there are some updates that happened for each and every record with a count of 1. But still I cannot able to figure out as to for which particular field the update has happened for each records.

Can 

Can anyone please help me out on this as this is very urgent for me as I need to showcase a demo on this to our customer on this process?

Thanks

[Jorn van Beek]

sorry Anshu,

that answer is not correct. Records in the sys_history_line table are only created when you look at the history of a record.

To prove this. take a record, update it, do not look at the history via the context menu. now try to find the records in the sys_history_line table.

If you want to see what is changed you really need to look at the sys_audit table. (note if you need to make a report, it is not good practise to use the audit table as report source).

And yes, I did made this mistake myself before and I learned it the hard way.

For snow,

There are options to make sure ServiceNow creates an overview of what is changed. But the question is do you really want to do that?

In a demo I would go for:

• showing a record is updated
• showing the new values are in line with the excel sheet
• showing you can see what is updated (via the history list menu option)

if you want to go fancier

• show the automation is working. (not sure if oracle will push the excel to ServiceNow or just stores it on a share from which ServiceNow will pick it up).
• Show a next step of not using an excel but using a SQL import bypassing the need for the excel in general.

for the question if you can provide a full overview I would ask what the added value is. the Requirement is the records are the same. and to be really technically from ServiceNow point of view not even that, from ServiceNow point of view the records need to be the same as the excel provided.

Generally if they want to have a full overview of the changed records they say they dont trust the reconciliation. On that comment you can answer:

1. A report will not change that. They will still need to check all records by hand if the changes are right. And yes doing so in Excel might be faster, but still is a lot of work.
2. You shown in your demo you can backtrack changes if an issue is noted. (the report does not note the issue). So if something is wrong the data is there to troubleshoot.
3. If they still really want a report, you can tell them it is possible to add an option to capture all changes, but are they willing to spend a X money in time to build and to maintain for it? I doubt the business case is there to do so.

[Anshu_Anand_]

I totally agree with you, for showing 1 record as from audit history is ok but showing all of them will be huge task and waste of time if the integration is perfectly working.

For example:- email changes he can show to the client 

that can be seen in audit history for a particular user from sys_history_set table 

and we can make the job run as "oracle" instead of system administrator