Linking Content

Content Query

Approach 

Store the content in a single list and use content query web parts to present views of the data in that list. 

Show Me 

Pros 

  • The list item only exists in one place; the target locations have read-only views of the content
  • Whenever a change is made, changes to the content at the target location is automatic and immediate

Cons

  • Depending on the implementation, users may not have rights to view content in the master list
  • The out-of-the-box content query web part is limited in how it presents views of the data; for example, it would be extremely difficult to present a calendar view
  • May require a techncal resource to modify the content query view.  Check out the community-developed Enhanced Content Query Web Part as an alternative

List Copy Feature

Approach: use the "Send To Other Location" feature to copy a file from one source list to one or more target lists.  Choose the option to prompt the user to update target lists when publishing a major version.

Show Me

Pros

  • Users can choose when to update content in the target location
  • Users can choose which list items to copy to target location
  • Users can be notified when the target location is updated

Cons

  • Cannot be applied at the list level; each list item must be configured to be copied to a target location 
  • Only works with document library type lists (documents, pictures, pages, etc)
  • Only copies when a major version of the source is created
  • Is not automatic; requires user to select the option to update target lists when creating a major version
  • A separate copy is maintained in the target lists; can get out of sync with source

Use a Workflow to Copy List Items 

Approach

Show Me

Pros

  • Can be applied at the list and list-item level (using conditions)
  • Can use conditions to provide-data driven control over when list items are copied to the target location 

Cons

  • A copy of the list item exists at every target location
  • Requires some technical knowledge of creating workflows with SharePoint designer

Put Shortcuts in target lists that point to source list

Approach

Upload an html document to each target list that contains a meta-refresh tag to the source document.  Note: SharePoint will not allow you to upload .url and .lnk files.  This approach falls into the category of workaround / hack.

Show Me

Pros

  • The content is stored in one source location

Cons

  • Difficult to maintain; the solution is target-driven, not source driven.  If the source is renamed or moved, all targets must be manually updated.
  • Requires some technical knowledge to construct the html meta-refresh

Use an event handler to copy list items

Approch

Show Me

Pros

Cons

  • Not as easy to maintain as a workflow created in SharePoint Designer

 

Leave a Reply


Linking Content

Content Query

Approach 

Store the content in a single list and use content query web parts to present views of the data in that list. 

Show Me 

Pros 

  • The list item only exists in one place; the target locations have read-only views of the content
  • Whenever a change is made, changes to the content at the target location is automatic and immediate

Cons

  • Depending on the implementation, users may not have rights to view content in the master list
  • The out-of-the-box content query web part is limited in how it presents views of the data; for example, it would be extremely difficult to present a calendar view
  • May require a techncal resource to modify the content query view.  Check out the community-developed Enhanced Content Query Web Part as an alternative

List Copy Feature

Approach: use the "Send To Other Location" feature to copy a file from one source list to one or more target lists.  Choose the option to prompt the user to update target lists when publishing a major version.

Show Me

Pros

  • Users can choose when to update content in the target location
  • Users can choose which list items to copy to target location
  • Users can be notified when the target location is updated

Cons

  • Cannot be applied at the list level; each list item must be configured to be copied to a target location 
  • Only works with document library type lists (documents, pictures, pages, etc)
  • Only copies when a major version of the source is created
  • Is not automatic; requires user to select the option to update target lists when creating a major version
  • A separate copy is maintained in the target lists; can get out of sync with source

Use a Workflow to Copy List Items 

Approach

Show Me

Pros

  • Can be applied at the list and list-item level (using conditions)
  • Can use conditions to provide-data driven control over when list items are copied to the target location 

Cons

  • A copy of the list item exists at every target location
  • Requires some technical knowledge of creating workflows with SharePoint designer

Put Shortcuts in target lists that point to source list

Approach

Upload an html document to each target list that contains a meta-refresh tag to the source document.  Note: SharePoint will not allow you to upload .url and .lnk files.  This approach falls into the category of workaround / hack.

Show Me

Pros

  • The content is stored in one source location

Cons

  • Difficult to maintain; the solution is target-driven, not source driven.  If the source is renamed or moved, all targets must be manually updated.
  • Requires some technical knowledge to construct the html meta-refresh

Use an event handler to copy list items

Approch

Show Me

Pros

Cons

  • Not as easy to maintain as a workflow created in SharePoint Designer

 

Leave a Reply