I would like to understand the term "hyphenated relationships" in Salesforce. Are these below "hyphenated relationships" in Salesforce?

  • Master-Detail Relationship
  • Lookup Relationship
  • Parent-Child Relationship

And also please help me to understand that for hyphenated relationships like Parent-Child and Master-Detail, we always refer to the "other" object first, then to the object in question. Please correct me if my understanding is correct.

  • I think you are asking how to reference children or parents from some target object. Is that correct?
    – cropredy
    Dec 14, 2016 at 19:04
  • 3
    Where did you find the term "hyphenated relationships"? Never heard it before Dec 14, 2016 at 19:20
  • 1
    You seem to have fallen victim to a language barrier, The term that sfdcfox used, "hyphenated relationships" really means relationships where two terms are separated by a hyphen. "Master-Detail" and "Parent-Child" fit this bill. "Lookup", obviously, doesnt. Dec 14, 2016 at 19:35
  • 1
    Actually, quite the opposite. Dec 14, 2016 at 19:43
  • 2
    @SebastianKessel There are many questions asked here about Salesforce that don't involve code. If code were the primary criteria for closing a question, then you could probably go back and close at least 25% of the questions in the database.
    – crmprogdev
    Dec 14, 2016 at 20:23

1 Answer 1


In sfdcfox's answer, mentioned in the comments on the question, 'hyphenated relationship' simply means a relationship type whose descriptive name contains a hyphen '-' (also called a dash, an em dash, or an en dash, depending on how wide the dash is).

'Master-Detail' (the hyphen is between 'Master' and 'Detail') and 'Parent-Child' (the hyphen is between 'Parent' and 'Child') are two examples.

It is not a separate relationship type, and the term is not used anywhere in official documentation.

  • One-To-Many is also "hyphenated relationship" then? Dec 14, 2016 at 19:43
  • One-to-Many is a property of a relationship in Salesforce, but is not strictly a relationship type in Salesforce. Generally speaking, any one relationship field has this one-to-many property. This particular term is uncommon on the Salesforce platform (it's more commonly used by database designers/administrators)
    – Derek F
    Dec 14, 2016 at 19:51
  • 1
    For example, say you have Opportunity and OpportunityLineItem (OLI for short). The relationship between Opportunity and OLI is a Master-Detail relationship (Opportunity being the 'Master' part or 'Master' side of the relationship, and OLI being the 'Detail' part or 'Detail' side) of the relationship. The relationship field itself resides on OLI, making it possible to relate many OLIs to a single Opportunity. OLI therefore has a many-to-one relationship to Opportunity. Conversely, Opportunity has a one-to-many relationship to OLI.
    – Derek F
    Dec 14, 2016 at 20:00
  • Clear to me. Thanks for the clarification. I was confused with the question mentioned in the post salesforce.stackexchange.com/questions/150205/…. My answer to this multiple choice question was: Lookup relationship. But it was mentioned One-To-Many as the correct answer. Dec 14, 2016 at 20:03
  • Both Lookup and Master-Detail are One-To-Many relationships. However, I agree with you that, in this case, Lookup is the correct answer. Dec 14, 2016 at 20:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.