Reltio Connect

Hi,

We are currently maintaining Physician's State license information in the HCP entity as a nested attribute with license number and state in Reltio. But when Veeva consumes that same license information, it wants to maintain that in the address object, so Veeva teams would want to tag the license to the address object in Veeva based on the license state information.

The SLN information is already stored within the address object and each record within the Address object represents 1 address per HCP

Has anyone come across this use case and implemented this through the Reltio SFDC connector? Need some urgent help, so any inputs are appreciated.

Hi Nikhil,

I can't remember the object schema within Veeva off the top of my head but within the Address object, is there 1 record per Account per Address? And the SLN is already stored within the Address object too?

-D

Hi Nikhil,

Refresh my memory as it has been a long time since I've worked within Veeva...

Within the Address object, is the SLN information already stored within that object? And each record within the Address object represents 1 address per HCP?

We are currently using a competing product that has an Account -> Account_Address -> Address structure.

-D

Hi David,

The SLN information is already stored within the address object and each record within the Address object represents 1 address per HCP

So if the HCP has a NY license, all NY addresses for that HCP should show that license on the address object

I should have paid closer attention to your question because I asked something you already provided information for. Apologies! :-)

Why do the Veeva teams want to tag the SLN in the Address object? The connector presumably is already configured to update the SLN's from Reltio to Veeva right?

Btw, we currently use the connector in a similar fashion but opted to use a Location entity type versus nest addresses so as a result, our SLN info is stored in a relationType.