The solution section provides an overview of how to solve this scenario, and why that solution was chosen. The Solution Steps section immediately following outlines the exact steps used to replicate the solution.
Solution:
To view the remainder of this content, you must purchase the Salesforce.com Certified Administrator Study Guide. Please Login or purchase the study guide.
Slight typo after step 5 – should be “on your own”
Hi John,
Hope you well.
This may be a silly question but why are we using a formula to directly fetch text from another object? I can understand if we were applying logic between the data being fetched but in this example all we are doing is fetching exactly whats there? For example account name on opportunity uses a “lookup”
Thanks
Matt
Because you can’t display fields from one object on another object directly in a page layout (you can kind of do this with lightning but not at all in classic). The formula allows us to copy the field from one object to another so that we can include it in the layout.
Hi John, is it possible to create a global variable in salesforce ?
Best regards and thanks for your amazing and helpful website.
Yes if you create a hierarchy based custom setting, you can reference them the same way (might be able to do this with custom permissions and similar functions as well, haven’t tried)- very handy for creating your own settings that you want to reference in formulas.
https://www.screencast.com/t/apFY4UUe03
Is it possible to get an Field wih an cross object formula which is the second Relation and not the first.
For example:
Article Quote — 1. Relation M.Detail — Quote –2 Relation M.Detail –Account
I would like to have the Accountname on Article Quote Object.
regards john
Yes formulas can span multiple objects
John, would a look up relationship between Account and Opportunity work in this scenario?
I was wondering the same myself? Unless the formula was the only way to convert the pick list value into something more meaningful, maybe?
Yeah- good question. There is language on the site that describes this phenomenon. Essentially the relationship between account and opportunity is a lookup relationship; however, it is not a “standard” lookup relationship, because it still allows you to create a rollup summary field.
Excellent!
This is probably a dumb question, but why in the formula are we entering the field as “Account.Type” and not, “Account_Type”? I see where you stated, “Account.Type” in the instructions and steps, but the field label is, “Account_Type”. Is this just a basic formula concept I need to learn?
Working through it more and I think I got it. Does “Account.Type” simply mean Account>Type when talking about using the Advanced Formula Editor vs. typing in the formula free hand?
Yep that’s exactly the case
Thanks so much for the quick response. Test is on Friday aaaaack! Great study guide though; it’s saving my hide right now. Big lightbulb moments.
There is a typo in step 5 – It should read “on your own” rather than “on you own.”
step #5 insert field > 1-opportunity 2 account, after that I don’t have the option of next , just close. Also TEXT (account) is not an option. It doesn’t populate onto the page. Thank you.
try manually typing in TEXT(Account.Type). This should work as long as you’re creating a formula field for one of the related objects i.e. Opportunity.
Thanks Karia.
@Erin, if you select Account (without the “>” then it will select the account id, you need to select “Account >” as shown above) – from the advanced formula tab.
Hope that helps!
Choose output type > chosing Text does not give the option of formula return type.