Calling
HTTP web service fails when calling non-SharePoint HTTP (REST) web service from
SharePoint workflow
When
a workflow developer writes a workflow that calls non-SharePoint HTTP (REST)
web service from SharePoint workflow, “Authorization: Bearer” is added to HTTP
header by default, which may sometimes result in “401 Unauthorized" error
response.
Workaround: A workflow developer explicitly needs to have
“Authorization” field set with empty string (“”) in a “RequestHeader” property
of “Call HTTP Web Service” action. This will result in suppressing the bearer
authorization header for this HTTP request.
Workflow doesn’t
support external list in SharePoint 2013
Workflow
in SharePoint 2010 supported create, read, update, delete (CRUD) operation for
external list but SharePoint 2013 workflow doesn’t support CRUD operation for
external list due to platform limitation.
Workaround: Try SharePoint 2010 workflow by using Start a
list/site workflow action inside the SharePoint 2013 workflow.
Workflow doesn’t
support Survey list
Workflow
in SharePoint 2010 supported create, read, update, or delete (CRUD) operation
for the Survey list but SharePoint 2013 workflow doesn’t support CRUD operation
for Survey list because of a platform limitation — Survey list doesn't have
GUID field).
Workaround: Try calling the SharePoint 2010 workflow by using
Start a list/site workflow action inside SharePoint 2013 workflow.