Gaurav,
I think we're talking about two different things. The function you provided merely returns the content (presumably a source code) that has been written to the attribute. Example: IQVIA OneKey provides the code SP.WUS.ANS to represent Anesthesiologist in the Specialty attribute. And let's further suppose that our instance of Salesforce (source = SFDC) writes its own code, "SF-HCP-ANES" into the attribute as one would expect (and btw the connector does this part just fine. I.e. when it retrieves a record from Salesforce it correctly retrieves the Salesforce code for the item held in the Salesforce attribute and stores it in the Reltio attribute.)
Now suppose the survivorship strategy has chosen OneKey as the winning source and thus the OV is the OneKey code of SP.WUS.ANS. (As one would expect the Reltio UI determines that the crosswalk for the current OV is "OneKey" and it uses RDM to transcode OneKey's code of SP.WUS.ANS to "Anesthesiologist" for display purposes.)
Someone now updates another attribute and it's time to send the record back to Salesforce. The lookup function you provided would merely grab the current code for the OV held in the Specialty attribute, which in this case is SP.WUS.ANS and send it to Salesforce. But that is useless information for Salesforce. Salesforce, like any source system, needs to receive codes it recognizes. In this case it is expecting "SF-HCP-ANES". The Connector should calculate this by leveraging RDM to do a reverse transcoding of the canonical item, Anesthesiologist, held in the OV back to the proper Salesforce code of "SF-HCP-ANES".
This can only happen if two things are occuring:
1. The Connector has to be aware of the source name used for the target system, in our case "SFDC"
2. The Connector has to leverage RDM and do a reverse transcode.
Make sense?
Thoughts?
--
Curt PearlmanPwC | Solution Architect MDM
Los Angeles | +1 (818) 445-5224
PricewaterhouseCoopers Advisory Services LLC
The information transmitted, including any attachments, is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited, and all liability arising therefrom is disclaimed. If you received this in error, please contact the sender and delete the material from any computer.
In the event the content of this email includes Tax advice, the content of this email is limited to the matters specifically addressed herein and is not intended to address other potential tax consequences or the potential application of tax penalties to this or any other matter.
PricewaterhouseCoopers LLP is a Delaware limited liability partnership. This communication may come from PricewaterhouseCoopers LLP or one of its subsidiaries.