Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
34 replies
Subscribers
5 subscribers
Views
11756 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
I am trying to execute example mentioned in forum to test "Copy a Document
sapnas
over 10 years ago
I am trying to execute example mentioned in forum to test "Copy a Document From Appian to SharePoint" functionality using connector functions-
forum.appian.com/.../Connector_Functions
Code / Example from forum connection and API parameters suitable to the my environment-
=load(
local!documentToSend,
a!dashboardLayout(
firstColumnContents: {
a!pickerFieldDocuments(
label: "Document To Send",
maxSelections: 1,
value: local!documentToSend,
saveInto: local!documentToSend
),
if(
isnull(local!documentToSend),
{},
load(
local!shpCopyDocumentFromAppianWriter: bind(
null,
a!shpCopyDocumentFromAppian(
scsExternalSystemKey: "sharepoint",
usePerUserCredentials: true,
hostname: cons!SHAREPOINT_HOSTNAME,
port: cons!SHAREPOINT_PORT,
...
OriginalPostID-112434
OriginalPostID-112434
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 10 years ago
I am suggesting that because I was able to reproduce the "Unable to retrieve RequestDigest from SharePoint to execute POST request" error in my environment by using the IP of my Sharepoint server instead of the hostname. Suggestions will always me made after testing and confirming that this can be the root cause.
Let me explain, why. Sharepoint servers have a concept called Alternate Access Mappings; only the URLs listed as Alternate Access Mappings are considered valid for the Sharepoint server. By default Sharepoint will use only the hostname:
http://mysharepointserver
but you can have as many alternate access mappings as you want such as:
mysharepointserver.mycompany.com
in your case it seems that you haven't configured access mappings properly therefore it's expected you get, for some requests (i.e. Appian connectors) that require to get the RequestDigest first, an error like this.
Simply configure your access mappings properly or update your constant to be
http://mysharepointserver
or
mysharepointserver.mycompany.com
depending on what your current access mappings are.
Attached you will see an example of me reproducing the issue.
Here's how you configure them
technet.microsoft.com/.../cc263208(v=office.15).aspx
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 10 years ago
I am suggesting that because I was able to reproduce the "Unable to retrieve RequestDigest from SharePoint to execute POST request" error in my environment by using the IP of my Sharepoint server instead of the hostname. Suggestions will always me made after testing and confirming that this can be the root cause.
Let me explain, why. Sharepoint servers have a concept called Alternate Access Mappings; only the URLs listed as Alternate Access Mappings are considered valid for the Sharepoint server. By default Sharepoint will use only the hostname:
http://mysharepointserver
but you can have as many alternate access mappings as you want such as:
mysharepointserver.mycompany.com
in your case it seems that you haven't configured access mappings properly therefore it's expected you get, for some requests (i.e. Appian connectors) that require to get the RequestDigest first, an error like this.
Simply configure your access mappings properly or update your constant to be
http://mysharepointserver
or
mysharepointserver.mycompany.com
depending on what your current access mappings are.
Attached you will see an example of me reproducing the issue.
Here's how you configure them
technet.microsoft.com/.../cc263208(v=office.15).aspx
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data