Hi All,
In CIT scenario, is it possible to compare values of variable before inserting and ignore only that particular variable if values are same.
Regards,
Sridhara.
Cybersecurity
DevOps Cloud
IT Operations Cloud
If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more
Hi All,
In CIT scenario, is it possible to compare values of variable before inserting and ignore only that particular variable if values are same.
Regards,
Sridhara.
Just to elaborate, compare values of source and destination mapped variables, if both or same, ignore only that particular variable of record and insert others.
Not sure I understand completely. Do you mean to ignore table record(s) completely or just an element of table record(s)?
ignore just element of the table records. we are inserting around 12 elements for each record. for example if current location is same as new location, ignore only location and proceed with inserting remaining 11 variables.
Still not understanding why as this seems like a complete waste of time, money, and development. The intent of a CIT scenario is to insert, update, or delete table records, so if a source element is the same value as a destination element, then this isn't really even an update and CIT scenario processing is not going to speed up drastically. In fact, processing speed could slow since obtaining destination value to be used for comparison.
But I digress. If you want to ignore a mapped element (ie. node), then review help for Function pifIgnoreNodeMapping(strMsg As String) As Long...
- amPortfolio
- lLocaId
IF SourceValue = TargetValue THEN
pifIgnoreNodeMapping()
ELSE
RetVal = SourceValue
END IF
Hi Mark,
Thanks for information. we have created a CIT scenario to push data from UD to AM. But there is a custom field in AM which is mandatory field but customer does not want it to be modified by the scenario. We had to opt for CIT instead of OOB integration as customer does not want vendor name(which is mandatory for OOB UD-AM integration) tom come from UD.
We are trying to retain the current information in that particular custom field or in other words, we want to reuse same value which is present in that custom field.
Regards,
Sridhara.