Skip to main content

Calculated fields on relationship rules

  • January 2, 2017
  • 6 replies
  • 52 views

jeffrey_coleman
Forum|alt.badge.img
I went to create a relationship rule with a calculated field and was shocked (shocked, I say!) to find that it wasn't an option.

It should be!

6 replies

sidhu
Forum|alt.badge.img+1
  • Gainsight Employee ⭐️
  • January 3, 2017
Hi Jeff, 

Thanks for this post. The following things that you could do for rules on Account cannot yet be done for rules on Relationship and we intend to achieve a full feature parity. 

1) Creating calculated fields (even for account rules, the calculated fields do not give reliable results when we have instance or user level data in source)
2) Choosing an account identifier when there are multiple fields on the source object looking up to an account
3) Including accounts where data in unavailable

Thanks, 
Sidhu

reneehouse
Forum|alt.badge.img+1
  • Contributor ⭐️⭐️⭐️⭐️⭐️
  • March 15, 2017
I agree with Jeff on this.  Do we know where this is on the roadmap?

cara_brill
  • Contributor ⭐️⭐️⭐️
  • June 19, 2017
This is now a need for our Gainsight use cases as well. 

manu_mittal
Forum|alt.badge.img+3
  • Gainsight Employee ⭐️
  • June 19, 2017
Thanks for posting, Cara! 

Do you think you'd be able to address your use-case using a Relationship Bionic Rule instead? We recently added a pretty robust formula builder under the "Transformation" task. Details are available here

cara_brill
  • Contributor ⭐️⭐️⭐️
  • June 20, 2017
Thanks, this may work, I will try it out now!

cara_brill
  • Contributor ⭐️⭐️⭐️
  • June 20, 2017
This doesn't seem to work as an option either b/c I cannot get a relationship ID into the transformation task and then I have no "Setup Action" options.