Response from Customer

[CISCO ENHANCEMENT REQUEST] Support update operation for load to relationship action

  • 16 March 2018
  • 3 replies
  • 22 views

Userlevel 3
Badge +1
Currently 'load to relationship' action performs upsert operation by default. So if there are many rules with this action and we have some identifier coming null or unexpected values, there is a chance of duplicate relationships getting created.

3 replies

Userlevel 5
Anton,

Can you elaborate some more on the use case? 

Regards,
Jitin
Userlevel 5
Anton,

Can you elaborate some more on the use case? 

Regards,
Jitin
Userlevel 3
Badge +1
Lets say they have a rule to update ARR field in GS Relationship, now if we use load to relationship action in its current form and one of the identifier (not using relationship id as identifier) turned out to be null or not matching an existing record it will straight away create a new relationship (which is not what they are expecting).
In Load to customers, we are explicitly using account id as identifier so this kind of a situation doesn't arise there.

Reply