Body: <p>Looking for documentation on D9 Views integration using advanced relationship features.</p>
  <p>Finding it difficult to determine which outcomes are a result of not understanding the various id joins and which are potential bugs.</p>
  <p>Willing to test and assist in documentation.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-04-30T19:35:09.237Z
Comments.Text: Can you add some examples of the sorts of issues you are hitting.
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-05-01T12:27:07.780Z
Comments.Text: Hmmm, where to begin.   Because there are so many options from setting up the basic view (e.g. contacts vs say participants) it is easy to make the wrong starting selection.   Some basic guidelines on usage would help a lot because the wrong first steps can lead to lots of things that don't work as expected.   On the Advanced relationships there are a lot of options for selecting what I assume to be joins (to make certain fields available to the view).  But the terminology used is confusing and seems to overlap in mysterious ways.   This list includes over 50 different options in itself
Comments.UserDisplayName: Dave T
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-05-01T12:29:06.447Z
Comments.Text: Image of list of relationship option added above
Comments.UserDisplayName: Dave T
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-05-01T12:32:17.163Z
Comments.Text: So, any type of documentation that helps sort out choices to make to set up fields available for view.
Comments.UserDisplayName: Dave T
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-05-01T19:45:33.780Z
Comments.Text: Your attempt to add image may not have worked. The issue of which entity to start a View with has not changes between D7 and D9. Yes using relationships to set up Relationships can be confusing and the terminology has changed. Fundamentally, if you have a contact then you need to add the Relationship Type, then add the related contact to that Relationship. But to help give more explicit documentation will depend on what entity you are starting with.
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-05-01T19:46:31.433Z
Comments.Text: am happy to try and take you through a specific example, which may then help build up some better documentation, or i can spin up a View and export it for you
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-05-02T02:16:39.833Z
Comments.Text: Let me see if I can create some more specific issues.  I have had some success with basic contacts but there has been a lot of trial and error and guessing.
Comments.UserDisplayName: Dave T
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-05-03T03:42:01.270Z
Comments.Text: how familiar were you with this in d7? the key changes are that whereas the d7 Views integration had a lot of in-built joins for getting eg phone, emails etc, in d9 you have to JOIN those tables deliberately
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-05-03T11:30:46.803Z
Comments.Text: Yes, exactly.   So, D8 made all entities eligible for joining and removed the simple built in joins.  We now have way more choices most of which have no value and overwhelm the simple stuff.
Comments.UserDisplayName: Dave T
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-05-03T12:25:23.543Z
Comments.Text: Perhaps documentation that specifically outlines how to do the 5 - 10 most common use cases would work.   Maybe a structure that allows others to add their "recipes" for specific use cases
Comments.UserDisplayName: Dave T
Tags: <drupal-views><relationships><drupal-9><documentation>
Title: Documentation for Drupal 9 Views Advanced Relationship usage
ThreadText: # Documentation for Drupal 9 Views Advanced Relationship usage
  
  (Asked by: username_0 on 2023-04-30)
  
  Looking for documentation on D9 Views integration using advanced relationship features.
  
  Finding it difficult to determine which outcomes are a result of not understanding the various id joins and which are potential bugs.
  
  Willing to test and assist in documentation.
  
  **Tags:** drupal-views, relationships, drupal-9, documentation
  
  > **Comments:**
  > **username_1**: Can you add some examples of the sorts of issues you are hitting.  
  > **username_0**: Hmmm, where to begin.   Because there are so many options from setting up the basic view (e.g. contacts vs say participants) it is easy to make the wrong starting selection.   Some basic guidelines on usage would help a lot because the wrong first steps can lead to lots of things that don't work as expected.   On the Advanced relationships there are a lot of options for selecting what I assume to be joins (to make certain fields available to the view).  But the terminology used is confusing and seems to overlap in mysterious ways.   This list includes over 50 different options in itself  
  > **username_0**: Image of list of relationship option added above  
  > **username_0**: So, any type of documentation that helps sort out choices to make to set up fields available for view.  
  > **username_1**: Your attempt to add image may not have worked. The issue of which entity to start a View with has not changes between D7 and D9. Yes using relationships to set up Relationships can be confusing and the terminology has changed. Fundamentally, if you have a contact then you need to add the Relationship Type, then add the related contact to that Relationship. But to help give more explicit documentation will depend on what entity you are starting with.  
  > **username_1**: am happy to try and take you through a specific example, which may then help build up some better documentation, or i can spin up a View and export it for you  
  > **username_0**: Let me see if I can create some more specific issues.  I have had some success with basic contacts but there has been a lot of trial and error and guessing.  
  > **username_1**: how familiar were you with this in d7? the key changes are that whereas the d7 Views integration had a lot of in-built joins for getting eg phone, emails etc, in d9 you have to JOIN those tables deliberately  
  > **username_0**: Yes, exactly.   So, D8 made all entities eligible for joining and removed the simple built in joins.  We now have way more choices most of which have no value and overwhelm the simple stuff.  
  > **username_0**: Perhaps documentation that specifically outlines how to do the 5 - 10 most common use cases would work.   Maybe a structure that allows others to add their "recipes" for specific use cases  
  
  ---
  
  ## 0 answers
  
  