You don’t see a lot of SharePoint poetry out there and there’s a reason for that – it would be terrible. However, some of you may enjoy a bit of terrible niche poetry on a Monday morning. For you yet-to-be-institutionalized folk out there I’m posting this piece that I wrote for a coworker. I run my company’s internal SharePoint Group and Mike was our featured speaker last week. Since our meeting invitations go out through the company news letter, I try to keep them from being too bland.
Michael McNett is McNuts about SharePoint.
He’s a fan of Fast Search and a Friend to refining.
Content types make him cry like he’s christened a son.
Extranets excite him and his eyes you’d see shining
If integrating InfoPath is the job to be done.
Populating profile properties is Mike’s thrill.
He loves publishing the perfect profile post.
His RoadMap is no ruse. If you need things done right,
It’s the best way to ensure that your timeline is tight.
The site is live and registration is open for the Microsoft Heartland Region SharePoint Conference 2013.
The conference will be at the Columbus Convention Center on March 21. My coworkers did a great job on the web site and I’m pretty pumped about giving two afternoon development presentations. WooHoo!
I have a SharePoint 2010 list with a custom InfoPath list form. Recently I needed to add a couple new fields to the list and thus update the form.
- Unfortunately #1) This is a simple task, so if something goes wrong, you won’t find much help out there.
- Unfortunately #2) Something went wrong.
I found that when I tried to republish my form, I received an InfoPath error dialog “The SOAP message cannot be parsed.” In fact, I found that if I just opened and, making no changes, published the form, it would also fail.
Not useful. So I fired up Fiddler in hopes I would be able to get a little more information about the error.
You can see above that my client is actually not receiving an HTTP error. Instead I’m receiving an error page, and a quick look at the url for that page shows that the actual problem is a timeout (/_layouts/error.aspx?ErrorText=Request%20timed%20out)
Inspecting the payload shows that this is the branded SharePoint error page.from the error page shows that the actual problem is a timeout issue.
#HeadSmack: Only now as I’m writing this up does it dawn on me that because the above response is the standard error page, I probably could have dug into the HTML there and pulled out the correlation ID and then traced the issue into the logs for more information.
Normally, you’d go to the logs for something like this, but in this instance, I don’t have direct access to the logs and without a correlation ID getting any info back is difficult. Instead I go to Bing I do find a few references to how this timeout duration can be changed on the farm. However, this form is already in place and I can’t even republish the same version. It didn’t feel right that I should need to change farm settings to correct the issue.
As far as I know, none of the form’s xml gets stored in with the actual list item. Still there were 2499 items in the list now, which is way more than there were when this form was originally created. If maybe the system took some action, be it validation or update, to each list item when the form was updated, a timeout would seem plausible. On a hunch I decided to try reducing the number of items in the list.
Starting with the items with the oldest modified dates, I began deleting them 100 at a time. With the intent on recovering them from the recycle bin if all goes well.
About 1000 items into the process my error message changed, which felt promising.
Then at the magic number of 1199: Success! WTF??! Oh well, I’ll take it.
So I made all of my updates, and republished the form. I then went back into the recycle bin and restored all the deleted items.
All the items came back fine without so much as an altered modified date. (It’s 2013 now. Those dates are a year ago. I’ll admit the coincidence of the timing did cause me a split second of panic.)
I don’t know why it should matter how many items are in the list and this is a hacky workaround, but in a pinch or with a reluctant admin, this may be the hack you’re looking for.
SharePoint has forsaken me, at least that’s what it feels like every 3 years or so when they release a new version. When it went from STS to WSS 2 it was “What, I can’t use the SQL DB directly any more?” Then came SP 2007 and, “What, I can’t make post release updates to my Site Definitions?” SP 2010: “I can’t develop on with Virtual PC anymore?”
Am I ranting here? Nope. I love it. I’ve been a SharePoint developer a long while now and each time I begin to get a little bored with the job, Microsoft introduces a new version of the product that upends the community. There are always new, exciting features and ‘features’ to learn, many of which are improvements .
Now SP 2013 is here and it’s awesome, so what’s moved my cheese this time around? Apps for SharePoint. I explained earlier why I think SharePoint Apps are critical and why I think they’ve killed Farm and Sandbox solutions (RIP SharePoint Features 2007-2010). So now I’m trying to create an SharePoint App for a common business scenario and I’m finding myself stuck rather early in the process.
I want to create a list template and deploy it as a SharePoint App. I want to be able to roll up content from multiple instances of my list, so all instances of my list must use a common content type. Creating a SharePoint App that includes my site columns, content type, list definition, and list instance is pretty straight forward, but here’s the big catch: I want instances of my list to live in right in the user’s site so the user can interact with it just like the OOTB lists they’ve added, including creating lookup fields. SharePoint Apps run in the application infrastructure, which is a separate site collection from the user’s site. Using all the simple methods in Visual Studio (Add Item) leaves a barrier between the user’s site and my list instance.
If When I figure this all out, I’ll turn it into a few step by step articles and maybe publish the final product to the store.
Oh, and Happy New Year!