Sitecore Pilipinas

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 ...

Part of the extra work in the SC upgrade process is making sure that your modules still work after the upgrade. Since we were using SPIF as one of our major modules, it was important that this was validated and updated as well. From our current 111115 revision, we chose to upgrade to 1.1 rev 130613. Installation was pretty straightforward we followed the SDN instructions nothing difficult there. What struck us though was the note in one of the upgrade path; it says, upon first access, any existing integration folder will be recreated. Whoa! This did not sound too refreshing to us as we already have thousands of references to these integration items. We had to find out a way to sync the refs once the upgrade completes, one route we took was to leverage the SC Links DB. We used the steps below: 1) After upgrade, rebuild the Links DB, since the web DB still contains the current live refs, we can use the media IDs here as refs once the SPIF in master has refreshed. 2) We then cre...