Its been a while since I posted anything, life has been rather busy. I have recently been working on a SharePoint Office 365 project, mainly concentrating on Workflow and Event Handlers (for lists). These are the things I have discovered!
Workflow
- Need to be reusable, in order to allow them to be saved as a template (from SPD 2010), exported, and re-imported into Visual Studio
- Can only use the declarative workflow, with this being sandboxed
- If you have several workflows, and want to deploy with a package created in Visual Studio (the namings of the feature otherwise are just awful), then don;t deploy the workflow list for the workflows you activate after the first (confused?)… set activation dependancies if necessary
List Item Event Handlers
- Can be a bit annoying! This may work fine locally, but give an “internal server error” when deployed to O365. This gives a correlation ID – which is really no help. I’ve found that *sometimes* after leaving the solution for 1.5 days (ish), and then returning to it, the event handlers magically work! I suspect that it may have something to do with app pool recycling, as on local deployments, I ocassionally need to do this.
- The exact same event handlers, in exactly the same package, seem to work fine on my personal O365 (E3 plan) without error, but not the one for the client. I have also created a new O365 on trial, and it deploys and works fine there also… this seems to point to an error at the Microsoft O365 end. A ticket has been raised, and I look forward to hearing the response.
