Reltio Connect

How to create a derived attribute from other attribute by using any formula/condition in Reltio ?

Example, we have attributes named "City_1"  and "City_2",  and we want to populate another attribute named "City". This new attribute "City" will take the value  from "City_1" if it is not null ;  otherwise,  it will hold the value from "City_2".  Is there a way to get create a derived attribute in Reltio ? 

How to create a derived attribute from other attribute by using any formula/condition in Reltio ?

Example, we have attributes named "City_1"  and "City_2",  and we want to populate another attribute named "City". This new attribute "City" will take the value  from "City_1" if it is not null ;  otherwise,  it will hold the value from "City_2".  Is there a way to get create a derived attribute in Reltio ? 

There is not a way to directly execute logic to generate the value which you would like to be put into another field, but there are several options which may accomplish similar behavior.  It could technically be done with a LifeCycleAction or a subscription to the change queue to calculate and write the new value in, but both of these methods would be executed on every change event and will create more significant overhead / latency than other method I will describe below.  Let me know if you need more details on them.

The simplest is the Pattern Based Cleanser. This will concatenate one or more values from other fields (optionally with any desired static text) to generate a value for a new field.  This is configuration which is added directly to your JSON metadata in the entity type you desire.  With this method only the OV from the source fields will be copied, and all values are copied without any conditional logic.

In your use case, the best way to accomplish your goal would be to use a survivorship rule on the first city field to selected the preferred value in that field, then use the Pattern Based Cleanser to copy that value into the alternate field.  The challenge to this method is that the first City field must leverage survivorship rules to determine the preferred value.  In this case if survivorship can accomplish the desired value in the first City, you may not need to copy it to the second.  

The least attractive method to to accomplish this logic in the ETL layer.  While it would be simple to accomplish with most modern ETL tools, it would only be applied to data ingested through that ETL pathway.  Data manually entered in the UI or loaded through other paths may not have the same logic applied.  The previously mentioned approaches are universal to any data change regardless of the ingestion method.  

How to create a derived attribute from other attribute by using any formula/condition in Reltio ?

Example, we have attributes named "City_1"  and "City_2",  and we want to populate another attribute named "City". This new attribute "City" will take the value  from "City_1" if it is not null ;  otherwise,  it will hold the value from "City_2".  Is there a way to get create a derived attribute in Reltio ? 

Dan,
I recognize this thread is a bit old, but I had some thoughts on how to accomplish something like this with a combination of a cleanser and RDM. In our case, we have configured Entity Roles, and we would like to be able to automatically set the Role based on the value of another attribute. 

In our Organization entity, we have an attribute called Company Type that is controlled using a lookup in RDM. What I am thinking is that when somebody enters the Company Type, I could use a cleanser to copy the same value entered into the Role attribute, but using RDM I could then translate the value of the Company Type entered into the appropriate canonical value for the desired role.

For example, a company type of "Retailer" might be translated to the canonical value of "Customer", and a company type of "Manufacturer" might be translated to the canonical value of "Vendor". 

What are your thoughts on this approach? 

There is not a way to directly execute logic to generate the value which you would like to be put into another field, but there are several options which may accomplish similar behavior.  It could technically be done with a LifeCycleAction or a subscription to the change queue to calculate and write the new value in, but both of these methods would be executed on every change event and will create more significant overhead / latency than other method I will describe below.  Let me know if you need more details on them.

The simplest is the Pattern Based Cleanser. This will concatenate one or more values from other fields (optionally with any desired static text) to generate a value for a new field.  This is configuration which is added directly to your JSON metadata in the entity type you desire.  With this method only the OV from the source fields will be copied, and all values are copied without any conditional logic.

In your use case, the best way to accomplish your goal would be to use a survivorship rule on the first city field to selected the preferred value in that field, then use the Pattern Based Cleanser to copy that value into the alternate field.  The challenge to this method is that the first City field must leverage survivorship rules to determine the preferred value.  In this case if survivorship can accomplish the desired value in the first City, you may not need to copy it to the second.  

The least attractive method to to accomplish this logic in the ETL layer.  While it would be simple to accomplish with most modern ETL tools, it would only be applied to data ingested through that ETL pathway.  Data manually entered in the UI or loaded through other paths may not have the same logic applied.  The previously mentioned approaches are universal to any data change regardless of the ingestion method.  

How to create a derived attribute from other attribute by using any formula/condition in Reltio ?

Example, we have attributes named "City_1"  and "City_2",  and we want to populate another attribute named "City". This new attribute "City" will take the value  from "City_1" if it is not null ;  otherwise,  it will hold the value from "City_2".  Is there a way to get create a derived attribute in Reltio ? 

Yes we have definitely seen this approach.  As long as there is a clear mapping between each field value and the RDM transcoding.  

Reltio now supports arbitrary ranking of values in survivorship rules (called Value Based Priority).  But before this option was available, customers could echo a value into a "shadow" attribute which was transcoded with RDM to a ranking value which used a Max survivorship rules. The original attribute could then use "other attribute crosswalk winner" to see which contributing value in the shadow attribute received the max transcoded value from RDM.  

In your case, you are just creating the shadow attribute to mirror the original, but receive a different RDM transcoding.  The copy cleanser should maintain the replication of the attribute, which RDM will maintain the transcoding.  The only time you may see challenges here is if the original attribute is a reference attribute.  Changes in a reference attribute value may not trigger the cleanser on the parent entity and hence not copy the value. 

You are suggesting you are leveraging "Role".  Reltio does have an out of the box "Role" profile role - which is slightly different than a profile attribute.  If you are leveraging this feature I am not sure how the cleanser will react to changes in that value (you just need to test it).  But worst case is to create a persisted Reltio attribute to mimic the same Role behavior.  

Cheers,

Dan

Dan,
I recognize this thread is a bit old, but I had some thoughts on how to accomplish something like this with a combination of a cleanser and RDM. In our case, we have configured Entity Roles, and we would like to be able to automatically set the Role based on the value of another attribute. 

In our Organization entity, we have an attribute called Company Type that is controlled using a lookup in RDM. What I am thinking is that when somebody enters the Company Type, I could use a cleanser to copy the same value entered into the Role attribute, but using RDM I could then translate the value of the Company Type entered into the appropriate canonical value for the desired role.

For example, a company type of "Retailer" might be translated to the canonical value of "Customer", and a company type of "Manufacturer" might be translated to the canonical value of "Vendor". 

What are your thoughts on this approach? 

There is not a way to directly execute logic to generate the value which you would like to be put into another field, but there are several options which may accomplish similar behavior.  It could technically be done with a LifeCycleAction or a subscription to the change queue to calculate and write the new value in, but both of these methods would be executed on every change event and will create more significant overhead / latency than other method I will describe below.  Let me know if you need more details on them.

The simplest is the Pattern Based Cleanser. This will concatenate one or more values from other fields (optionally with any desired static text) to generate a value for a new field.  This is configuration which is added directly to your JSON metadata in the entity type you desire.  With this method only the OV from the source fields will be copied, and all values are copied without any conditional logic.

In your use case, the best way to accomplish your goal would be to use a survivorship rule on the first city field to selected the preferred value in that field, then use the Pattern Based Cleanser to copy that value into the alternate field.  The challenge to this method is that the first City field must leverage survivorship rules to determine the preferred value.  In this case if survivorship can accomplish the desired value in the first City, you may not need to copy it to the second.  

The least attractive method to to accomplish this logic in the ETL layer.  While it would be simple to accomplish with most modern ETL tools, it would only be applied to data ingested through that ETL pathway.  Data manually entered in the UI or loaded through other paths may not have the same logic applied.  The previously mentioned approaches are universal to any data change regardless of the ingestion method.  

How to create a derived attribute from other attribute by using any formula/condition in Reltio ?

Example, we have attributes named "City_1"  and "City_2",  and we want to populate another attribute named "City". This new attribute "City" will take the value  from "City_1" if it is not null ;  otherwise,  it will hold the value from "City_2".  Is there a way to get create a derived attribute in Reltio ?