Tag Info

New answers tagged

0

You can use The Open Data Protocol or OData to retrieve data from your SharePoint. OData is a Web Protocol created on top of Web technologies incluiding XML,Atom,JSON. So you can retrieve the information from your SharePoint using OData in form of Atom entries. You can take a look at the following ling from msdn blog. ...


1

There are certain recommended hardware given by Microsoft. Depending on the traffic you get to your SharePoint server you may need to scale your hardware. Writing to a custom list is the general and the safest method considering the set of operations supported by lists. If the server side object model is slowing you down, you can use the Javascript client ...


2

First of all, you have an update panel. With that you have a few options. You could wire up a server side event to your button and hide the div on button click. The button click would cause an Async Postback which would just update the content inside of your update panel. One issue with your code is you are using normal html elements. To make your ...


1

Well, you can still register scripts in a Web Part through the ScriptLink control: <Sharepoint:ScriptLink ID="ctlScriptLink" runat="server" Name="file.js"></Sharepoint:ScriptLink> You can also just embed the JS in a script tag in your web part for the time being to test if the code works (or use a content editor web part on the page). ...


1

This should work. $('#Hide').on('click',function(e){$('#div000').hide(); }); $('#Show').on('click',function(e){$('#div000').show(); }); Add this inside the page load event.


2

It depends on what you want to do with the data, I'd say. In general, I would recommend the custom list approach, especially if the purpose of the form is to collect data and use it later. Recently, I built a custom 'poll' web part that did just this - I had a PollResponses list that stored the choice the user submitted through an AJAX request, and then I ...


1

The good thing with using ASP.NET is you can write your own logic and customize it whenever needed with much flexibility. It is relatively difficult than using InfoPath as we have to be concerned about the page life-cycle a lot. Also you can manage it easily with asp:view controllers when a large amount of components are there. (In your case 300) But on the ...


1

I am not involve in IP form designing but i know one of our department create IP form with tons of fields which slow down their site collection. Personally, As we know, this is last version of IP so i think better to design in ASP.net or access form. Check this post, they discuss couple of limitation. Disadvantages of implementing InfoPath in SharePoint ...


0

SPFieldUserValueCollection userValueCollection = new SPFieldUserValueCollection(SPContext.Current.Web, SPContext.Current.Item["Field"] as string); if (userValueCollection.Count > 0) { MypeopleEditor.CommaSeparatedAccounts = userValueCollection[0].User.LoginName; ...


1

Separating the recipient addresses by commas is acceptable: http://social.technet.microsoft.com/Forums/office/en-US/e68c8f84-cd95-4d9f-bcdf-2609b9cdf315/sending-one-email-to-multiple-recipients-only-one-gets-the-email?forum=sharepointgenerallegacy You may want to try the same troubleshooting steps as shown in the accepted answer: The string format of ...


0

The method on MSDN doesn't explicitly say how to delimit the users, standard convention is semi-colon delimited. If you are using commas and it isn't working, switch to semi-colons and see if that resolves your issue.


1

This has worked for me in the past: private SPListItem CreateLinkToDocumentPage(SPWeb web, SPList docLibrary, string pageName, string url) { SPContentType contentType = web.AvailableContentTypes[SPBuiltInContentTypeId.LinkToDocument]; //get full path of the document to add string filePath = docLibrary.RootFolder.ServerRelativeUrl; SPFolder ...


0

How are you fetching values for left side list box? Anyway you should be able to do this using normal html list box and javascript to move items left to right.


0

It seems that the content is retrieved dynamically via CSOM or REST, in that case it could explain why it happens. The access to CSOM/REST in anonymous context is not allowed in SharePoint 2013 by default, please follow What Every Developer Needs to Know About SharePoint Apps, CSOM, and Anonymous Publishing Sites article for an explanation and the solution ...



Top 50 recent answers are included