on 05-07-2013 8:41 AM
Dear All,
We want to enable "Skip Unchanged Records" property for Data Import.
Now there is a confusion regarding the statement mentioned in reference guide i.e.
Skip Unchanged Records
True/False. If set to True, records updated by an
import will not receive a change timestamp
if their field, cached qualifier, or tuple field
data values are not changed by the import.
Import- and syndication-tracking timestamps will
also be skipped. Skipped records are still
recorded in the Import log, however.
Note: Attributes, non-cached qualifiers, and key
mapping values are not covered by this
parameter, and any import to these data types
will trigger a record change timestamp, whether
the data values in the record actually change as
a result of the import.
According to above any change/same data import to Key Mapping value will change the time stamp field.
But when we try to import the same key mapping , we didn't see timestanp fields changing.
Also, according to our understanding Key mapping value don't change time stamp field as this is not present in the selected fields during creation of time stamp field.
Is there any other parameter which we are missing here ?
Please let us know your views on this.
Thanks.
Hi Ranjeet,
Please update/close the thread.
Thanks,
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Ranjeet,
What you are saying here makes sense.As per the document this holds when "Skip unchanged records" parameter is set as TRUE.
This line says -
Note: Attributes, non-cached qualifiers, and key
mapping values are not covered by this
parameter, and any import to these data types
will trigger a record change timestamp, whether
the data values in the record actually change as
a result of the import.
Let me try to set up few hypothetical scenarios where it should hold true -
case 1- If a record does not have remote key value and you map it on import.Only new value coming in would be remote key value as other values are same.Matching field is any field other than Remote Key.Import action is Update Mapped/Null.This should create a timestamp change.
case 2 - If record if remote key exists but a new remote key is imported for same or different remote system,timestamp change should result.(Remote key is not matching field and import action is Update Null for pre-existing records)
case 3 - If same remote key is imported and all values of other mapped fields are same.Timestamp change does not occur - As reported.
I would ask you to test this by changing the matching field.
If on changing the matching field timestamp change occurs then we are good else this goes as an exception to the above statement.
Please update your fidings.
Thanks,
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.