New answers tagged

0

If you're hosting your own page as a form, you could use the REST-API from the server. This would enable you to use a techical user to access SharePoint. REST-APIs are usable from any language (PHP, Java, etc.) If you're hosting your own page as a form on an asp.net-enabled server you could also use CSOM. Again, this would enable you to use a techical user ...


1

By web form if you are referring to a .Net page, you could use CSOM to connect to your site and create a new list item. MSDN article on CSOM Another great idea would be to use REST API if you cannot have managed code. Research a bit and you will be able to make a choice.


0

Solution for the issue is. Install hotfix http://support.microsoft.com/kb/2516485 ( you may already have this hotfix in your farm) on all WFEs. This is necessary so that the “userName()” function in InfoPath will return a result in domain\username format, instead of just username. In SharePoint Central Administration, create a new “Group” Secure Store App, ...


0

I was able to use the GetUserProfileByName of UserProfileService.asmx to get information for users even if they are not in the site collection. https://msdn.microsoft.com/en-us/library/aa981482(v=office.12).aspx


1

SharePoint installs on top of ASP.NET, itself built on top of IIS. Also, some specific modules (to handle Windows authentication, ...) needs to be activated in IIS. All these prerequisites are automatically installed (if needed) by the SharePoint Prerequisites installer. But SharePoint does not actually modifiy IIS binaries.


0

Copy.asmx service is for copying files from one SharePoint site to other. Its not for copying data from a physical location to SharePoint. Check this: https://msdn.microsoft.com/en-us/library/copy(v=office.12).aspx


0

The Search Service Application Proxy does probably not exist in the farm. The Search Service Application Proxy is responsible for the communication between the WFE's search web part and the Search Service Application on the application server. Create a new proxy using PowerShell cmdlets: Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction ...


1

An issue is solved! I tried the same WF at a site level (previously it was at a list level) and it completed without any problems. After that, I recreated a list and bound the WF to it. Now I suppose that the issue was related to some permissions on the original list. Thanx! Alexander


0

The Accepted solution has the best approach in it, which is make a call to a default home page at first so user is promoted with authentication screen, after authentication do a redirect to you HTML5 App. In a similar scenario i adopted a different approach, created a Proxy Service with c# which would do the authentication to SharePoint, could be accessed ...


1

You can use SpServices to achieve this, it will happen in 2 steps: Get all list names in an Array (below I'm logging it but you'll need to push it to an Array) $().SPServices({ operation: "GetListCollection", completefunc: function( xData, Status ) { console.log( Status ); console.log( xData.responseText ); $( ...



Top 50 recent answers are included