New answers tagged

1

InfoPath Form Services does not support claims based authentication (that's what MS Support told us, when we faced a similar issue with Nintex Workflow.asmx about a month back). If you look in the IIS logs you will see that the calls to the UserProfileService.asmx are getting made as nt authority\anonymous user instead of the currently logged ...


1

The key differentiation I see between the provider hosted app and standard in browser stuff, is the provider hosted model gets you a slew of other capabilities. You are spinning up a web application in Azure or locally where you can write your own custom APIs to integrate into your own systems or other routine timer job type functions. Using the web layer ...


2

The best way I could find to debug the SharePoint Web Proxy is to use an Azure API management gateway, configure that to point to the real resource, and then point the SharePoint Web Proxy to that gateway. Using that approach I was able to catch all the traffic on the other side of Sharepoint and figure out what its problem was.


0

Create Data Connection and Receive data from list you want and set the fields default value as the received data from the Data connection


0

https://<site url>/_api/web/lists/getbytitle('ListName')/items?$select=Author/Title&$expand=Author Since Author is of type user which is stored as User id in the column when used with expand function it retrives Title of the Author, you can also use ID, FirstName,LastName,LoginName as required.


0

I managed to find the issue. Instead of using Author as a Lookup field I just needed to use AuthorId as normal field. So the url is like https://<site url>/_api/web/lists/getbytitle(My List)/items?$select=id,Created,AuthorId This returns the correct result.


2

Create EndPoint workflow variable with value [%Workflow_Context:Current Site URL%]]/_api/Web/SiteUserInfoList/items?$filter=(ID eq [%Workflow_Context:AssignedTo%]) Add Build dictionary action to get the the response in a JSON format you will have to update the Accept and Content-Type http headers of your Rest http call; more specifically: Accept : ...


0

Apart from the Authorization empty in the RequestHeaders , set Content-Type and Accept to Accept : application/json;odata=verbose Content-Type : application/json;odata=verbose Check this for more info Check in the web service properties that the RequestHeaders points correctly to your dictionary that contains (Authorization,Content-Type and Accept). It ...



Top 50 recent answers are included