Archive for the ‘SharePoint’ Category

I’m not sure how this happened yet, but after doing some cleanup yesterday in a custom Web Part page that contains links to the jQuery CDN, this morning I looked at my page and the “tabification” courtesy of  jQuery UI was missing, and I had a mess of random HTML scattered all over the place.

At first I thought I had deleted a necessary resource as part of the cleanup, but upon closer inspection in SPD, I found that the prefix (//code.jquery.com) to all of my script references had been stripped out and turned into relative references, which of course could not be resolved.

Below is the correct format, plus a reminder comment for the next time it happens:

The correct URLs, plus a reminder of the correct format

The correct URLs, plus a reminder of the correct format

 

I’ve been doing more experimentation with SharePoint 2010 REST API, and as part of the process, ran into a problem I’ve seen intermittently before, but never delved into.

The issue was that my client REST call from within a SharePoint page would not refresh on some machines with Internet Explorer 11 until I opened the browser Tools. It was fine in Chrome, and on different machines with IE 10 installed, so I decided to investigate (Google) the problem. (more…)

Query and filter options for working with SharePoint 2010 REST API.

Scroll down the page to Tables 1 and 2 for a summary.

I wanted to prototype using the SharePoint 2010 REST API for List Data, and ran into a bizarre error in my DEV/TEST site collection. In this case, I am a Site Collection Administrator with no farm-level access.

(more…)

I’ve been working with WebAPI to implement a simple REST data service over http: as part of prototyping a client-side connection to an external system from SharePoint 2010.

I was able to get the data service running and accessible in Azure very easily due to some excellent tutorials from MSDN, and was able to bind the JSON data from my service to a simple chart from AmCharts that worked well in a test page. (more…)

I’ve been having lots of problems connecting to my OneNote notebooks that are published to SharePoint.

Specifically what will happen is that I get the OneNote message for a password, click on the message to open the dialog, enter my credentials, then it fails. Afterwards, OneNote stops displaying the password dialog and it will not synchronize. Usually, rebooting the computer will fix this problem, but that’s pretty extreme.

The problem occurs most frequently when I change my connectivity, e.g. stop using VPN or direct corporate network connection, and just connect over the internet via https. It happened again yesterday under these circumstances, and I didn’t want to reboot, so I did a little research.

What “seemed” to fix the problem was to simply restart the Web Client service on the local machine, as described in this article. It refers to adding registry entries, but I just tried restarting the service, which appeared to solve the problem. I may revisit the registry hack if I find that the service restart doesn’t resolve the problem reliably.

Update 8-21-2014: Restarting the service does seem to resolve the scenario described above very reliably. Note that you may not have sufficient permissions on your local machine to restart services. If this is the case, a reboot may be the only alternative.

After setting up my SharePoint 2013 Development Environment and creating a the simplest possible SharePoint-hosted “Hello World” application to test out my store and App Catalog settings, I was surprised and disappointed to find that my application, while successfully deployed, was missing all of the common SharePoint script and style resources.

As it turns out, the problem was that I did not create a Site Collection at the root level when I was running the initial setup. Thanks to Prem for the simple solution.

 

In order to delete every item from a SharePoint list using the Client Side Object Model (CSOM), it will likely be necessary to implement paging using the ListItemCollectionPosition property to avoid exceptions related to the size of the query/response.

While some of the old MSDN documentation recommends retrieving sets of up to 2000 items, I ran into problems with numbers anywhere near that large, before finally settling on a row limit of 250. Also, it doesn’t seem possible to optimize the Load method via lambda expression to retrieve just the ID field and ListItemCollectionPosition property. Maybe it is possible, but I gave up when it returned a MethodNotSupported (or something like that) exception. (more…)

Here are some resources to help with setting up SharePoint 2013 development environments:

SharePoint 2013: Creating a Development Environment — a TechNet wiki with numerous topics related to setup and configuration, part of a larger Best Practices posting.

Setting up a SharePoint 2013 Development Environment 101 — a TechNet blog post with other helpful hints

SharePoint 2013 Development Environments — Matthew Bailey’s blog with lots of links to other posts and information about pre-configured virtual resources

Set up the development environment for SharePoint 2013 — an MSDN article with still more resources and guidelines

Nintex Workflows offers some very nice capabilities related to querying SharePoint lists and obtaining collections of results, then operating on the collection in a variety of ways, including a very flexible For..Each operator. In this demonstration, however, another collection operation, Join, will be used to build a string of email addresses that can be sent as a single email.

In my case, I need to build up a “To:” list dynamically, which I could do by querying a list and using For..Each on the results, except that I need to send a CC along with each message. To avoid sending my CC list a message for each address that I find, I will join the addresses into a single, semicolon delimited list and send exactly one email. (I am assuming that Nintex is not smart enough to only send one CC for the whole bunch if I were to use For..Each) . (more…)