[CISCO ENHANCEMENT REQUEST] Support update operation for load to relationship action
+4Currently '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.
Anton,
Can you elaborate some more on the use case?
Regards,
Jitin
Can you elaborate some more on the use case?
Regards,
Jitin
Anton,
Can you elaborate some more on the use case?
Regards,
Jitin
Can you elaborate some more on the use case?
Regards,
Jitin
+4Lets 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.
In Load to customers, we are explicitly using account id as identifier so this kind of a situation doesn't arise there.
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.