Skip to main content

SharePoint Integration Framework (1.1.0 rev. 130613) for Sitecore - Use Cases

If you were wondering how a non-bi-directional SPIF works in different use cases, you may want to look at the table below based from my testing.



# Sharepoint Changes Supported? SPIF Notes
1 Folder created Y Folder created Do not name the folder or file with special chars like "-"
2 Folder deleted Y Integration folder is deleted This deletes any items in the folder
3 Folder renamed N Rename not supported Refrain from renaming folders in Sharepoint to avoid confusion - it wont get renamed in SC
Folder is still connected and any items added or updated under it gets syncd
  3.1 Upload File  Y File is pulled into SC similar to #5 Still syncs even though folder name is different
4 Folder Moved? N Folder is deleted Gets recreated as a new folder in the target location and any items under it
5 File uploaded Y File is pulled to SC
5.1 File updated Y Updated file is pulled into SC SP Overwrite\\keeps its GUID and refs
6 File deleted Y File deleted in SC
7 File renamed N Rename not supported File is still in sync, eventhough the name is different 
8 File moved? N File is deleted in original location File is recreated in the target as a new media item
Sitecore Changes SPIF Notes
1 SP Integration Item Clicked Checks with SP Doc Lib for any updates Statistics is updated with user who last triggered a check
2 SP Integration Folder Clicked Checks with SP Doc Lib for any updates Statistics is updated with user who last triggered a check
3 SP Integration File Clicked Checks with SP Doc Lib for any updates Statistics is updated with user who last triggered a check
4 SP Integration Item Manually Edited (re-Attach) Just gets overwritten on the next run
5 SP Integration Folder Deleted Gets recreated in the next run (with new GUIDs)
6 SP Integration Folder Renamed Still gets sync'd Looks like the integration is still valid as long as the original item exists in SP
7 SP Integration Folder Moved Gets deleted (not recycled)
The original location where the folder once lived is recreated though		 The same main parent integration tree
8 SP Integration File Renamed Still gets sync'd Looks like the integration is still valid as long as the original item exists in SP
9 SP Integration File Deleted media item gets recreated (with a new GUID) on next run
Note: SPIF is NOT bi-directional
Labels:

Comments

Post a Comment

Popular posts from this blog

Add Export to File Functionality in Sitecore's Search Options

One of our business users was requesting for a listing of items they've already added and have it available in a format that can be opened in a spreadsheet (Excel). My initial thought was to create a blank aspx page and write all the logic to get the data in the code-behind, run it and save the resulting file to a csv then I'm done. But then it got me to think, it might be a better idea to have this functionality plugged in to Sitecore and made available for everyone to use.  Sitecore Bucket's Search Options fly-out seemed a good candidate for this feature (See image below). So doing some quick readings I got myself in to the "zone" and started implementing this quick and dirty PoC. Just to explain what it actually does. User will basically do a search, ( Note that all search options require some filters or search keyword before any of the options can be used ) clicks the Export to File, it pops up a dialog to confirm the action and executes, after w
7 comments
Read more

Add/Allow a different media URL prefix in Sitecore (aside from tilde ~) in Sitecore 7.0

We recently had a requirement when one of our external vendors required that our media URLs should not include the "~" in the link as their system could not process those correctly. I found a few articles in the web, but most of them would suggest changing the default behavior, i.e. any "new" media item would have the 'new' replacement character though still supporting the tilde "~". Based on the web articles, I started with the following config keys and section: Media.RequestExtension Media.MediaLinkPrefix customHandlers We did not want to change any of the default behaviors, we just needed a way to make Sitecore support the additional URL media prefix. While sifting through the configuration, I chanced upon the following section: <mediaPrefixes>  According to the comment above it: Allows you to configure additional media prefixes (in addition to the prefix defined by the Media.MediaLinkPrefix setting)            The
Post a Comment
Read more

Brightcove Index Configuration for Coveo for Sitecore

We recently moved our search provider from using Endeca and Lucene to Coveo for Sitecore. One of the areas that broke was the Brightcove index. You may follow the sample below to be able to get your Brightcove index working again:  1) In your Brightcove contentsearch config, comment out or remove the sections highlighted below 2) Replace this with the one below: 3) Check the comments in the image above to determine what to use for your DefaultIndexConfiguration 4) Comment or remove the entire section/block 5) Your final config may look something like below Hope this helps someone. Thanks for reading.
Post a Comment
Read more