Several months ago I stumbled into an issue. I had OData data source with events and had to connect it to Outlook. Usually, it is a very simple task to map a content type to Office Item Type using SPD. However, for a while, SPD can’t work with OData at all. So, it was impossible to use common tool for that.
After three days of unsuccessful googling and asking how to achieve it everywhere 🙂 I tried to investigate it myself and found a way to do it!
Today, I stumbled into an issue. I copy-pasted some part of SPD 2013 workflow to another one. Both WFs are located on the same site and both uses lists which contain the same fields. After pasting I had to fix only step transition parts (on the bottom of every step), but after that the check WF for errors passed well. However, the new WF always failed with the following error message:
In this post I want to collect typical questions, which have high chances to appear if you implement custom SharePoint 2013 ASP.NET task form. I am planning to update this post as soon as I find new information which could be usefull for others. If you have some ideas, what questions and solutions should be included in this post, don’t hesitate to write a comment. Also, if you have a better solution for questions here, please, let me know. It could help us a lot!
Table of contents.
Q1: How to get a reference to a related item from SharePoint 2013 task form?
Q2: Why can’t I update my workflow which was created in Visual Studio?
Q3: Is it possible to use InfoPath task forms in SharePoint 2013 workflows?
This is the second post of the series related to SPD 2013 Workflows. In this post I will show you how to implement custom ASP.Net task form and embed it into your workflow. Some parts of this task are straightforward; However, there are several pitfalls and changes from SP2010.