I had an interesting error come across today when I was working on a new Nintex form list. I have been doing some power user training in my company lately and a few of my users have taken the plunge and started creating their own electronic forms in Nintex.
Which is awesome! It’s a great feeling when you demonstrate something to someone in a training session and then see what they are able to go and create on their own.
In this case, though the user had designed a great looking form, but when they went to submit the form once it was complete it gave the following error:
Which was very odd as I had never seen an error that gave all zeros for a correlation id on and error in SharePoint.
So I started to do some digging online and I noticed this was a common question that has come up before for several users in the past, but no one online I had seen had dealt with this in the context of creating and submitting forms.
After some more research I had a hunch that this was being caused from a required field on the form that was missing data when the form was being submitted. So I checked the form in Nintex form designer, and sure enough!
I saw that the “Title” column was not on the form, but in the list settings was still set to the required option like it is out of the box in SharePoint.
So I went into the list settings and turned off the required setting for this column and then went back to the form and tried submitting it again.
Everything submitted as it was supposed to and now I can move onto more form troubleshooting.
I hope this helps anyone else who runs into this error again and if you have any thoughts or comments, please feel free to add them into the blog.
On June 17th I had the pleasure of attending another great SharePoint Saturday event put on by one of the best users groups in the area and it did not disappoint!
The morning Keynote was given By Stephen L. Rose from the OneDrive for Business team at Microsoft.
It was really great to see from him all the new features and functionality that are coming ahead in just the next couple of months! Its something I think that will make users of OneDrive want it even more!
I also attended several other session about workflow and forms with Laura Rogers which was a great session describing all the ins and outs of how Flow is developing into quite a nice tool that still has a ways to go in certain areas, but is quickly being developed into an actual SharePoint Designer replacement.
There was also a great Power Apps session given by Laura later in the day where she went through some great scenarios and examples of how the current version of Power Apps compares with InfoPath as well. It can do some great things right now, but as with Flow, it still needs to be fleshed out I think more in order to be an actual replacement for the older tools everyone is used to.
Much of the content I saw from this day definitely centered around more of the push to Office 365, but what excites me even more is being able to mold these features and capabilities to the on premises and hybrid worlds of SharePoint.
Thanks once again to the Atlanta SharePoint group and all of the volunteers who work at this event! It was another great day of training that I learned more than my brain could hold. 🙂
If you work like I do trying to setup test environments in SharePoint often, the experience is great when you finally get all the bells and whistles activated for the features you need to test, but then what?
Now you have a great looking environment with no data! A SharePoint farm with no data in it is like a chocolate chip cookie without the chocolate chips in it. You might as well throw it away and go get something else to eat.
Never fear though as I have recently discovered a great tool that can auto generate much of the content needed to flesh out a SharePoint farm and it happen to be an open source project on GitHub created by the same fine folks that created SPDocKit!
It’s called SPDG (short for SharePoint Data Generator) and it’s another awesome tool to add to your arsenal if you don’t already use it.
Just head over to Github at the following link and check it out here!
Below is an example screenshot to give you an idea of what it looks like:
What is even better about this tool is that you can use it to generate as much content or as little as you need to flesh out your test box. It works with SharePoint Online, and even older versions of SharePoint like 2010!
This tool is so great and I can see so many uses for it, I may just have to do a demo video of this sometime down the road, so stay tuned! I’d love to see more folks talking about this because it definitely saves a lot of time and effort to fill up an empty farm when you need to give a demo!
Many thanks again to the guys over at SysKit for developing something awesome like this!
I hope you enjoy it as well!
I had an interesting request by someone the other day. I was helping them set up a new site template for SharePoint 2013 and they wanted to display a couple of reports on their site that they had in pdf format in a way to showcase the numbers of the report to others in the company that would visit this site.
There are multiple ways actually to do this very method, but the one I ended up going with is referenced in the following article:
After doing this one the page it gave a pretty good layout on the page. My only concern going forward is having to update this manually and having to possibly retrain someone to keep this showing the most up to date info on the page.
There are other things I would like to research as part of this like putting in zoom or other capabilities in the code to modify the view of the pdf for the users.
I hope this gives you more ideas for displaying info on sites and pages and should work regardless of what version of SharePoint you are working with.
If you have interesting ways to display reports or other objects on pages, feel free to add to this in the comments below.
Beau Cameron just posted a fantastic article about how to do this in O365. Here’s the link:
Recently I was working on a migration of a couple of big sites moving them to their own content databases and it didn’t exactly turn out as I planned.
So more than anything, I wanted to use this post to describe what happened and mention some tips and other things that may help others out in the future if you ever run into trouble when trying to break out sites into their own databases.
Here are the major events that happened in the migration process:
- Created DB under central admin
- Used Move-SPSite to move one site from another content database
- Content stuck on Move-SPSite, never finished
- Restarted all servers
- When came back up, new destination database was in recovery
- Recovery process used all SQL resources, major slow down of farm (sad time)
- Looked into SQL logs to check status of recovery thinking new destination database would come back up
- Actually after recovery finished, I still had no access to content created in new content database
- Checked and under central admin checked site locks and quotas
- Turns out entire site still on old source DB
- Hadn’t been copied over, even though SQL showed a populated database
- Site lock had been switched on all the way to no access
- Users going to site would get a 403 forbidden message when trying to access
- Went under site locks and cleared the lock
- Once this was done, content access returned to normal
- Original content and under Central admin still said content was on source DB
- New destination content DB under still showed also that it contained no content
So in the end, the big lesson learned here was that even though I could check SQL and see that the new DB contained information, SharePoint hadn’t moved the site over to the new content database.
I did some research and there are timer jobs that run gradual site deletions, but I don’t think they applied here. Either that or I switched back to the original database before anything else was allowed to happen.
In the future, I may just use Backup-SPSite along with Restore-SPSite because that command also has the ability to specify a new database to put the site into when the backup is restored.
I hope these tips save you some time and headaches in the future.