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!
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
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
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.
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.
Reply
Login to the community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.