Today I had a problem with a group of users that were trying to work with a very large PowerPoint file in SharePoint and didn’t realize until I downloaded a local copy of the file that it was too big to work with through Office Web Apps.
So I did some digging around to see if there was a way to possibly shrink the files, so I ended up finding something here:
In PowerPoint 2016 you can find the option here:
After doing a bit more digging, this actually applies to all Word, Excel, and PowerPoint versions from 2016 on down to even the Office 2010 versions.
So now I’d be curious if this could be automated somehow to do some major cleanup in PowerShell or something? Hmmm… maybe for another blog post later… hehehe.
Hope this helps if you need to free up some space in the future.
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.
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:
I wanted to take some time and just thank everyone who came to hear me talk about SharePoint today at the Chattanooga Portals and Collaboration user group.
I really enjoyed the stories that we all shared and some of the ideas we threw around to get more people talking about SharePoint in our corner of the woods.
If you have any questions or would like to see this talk given again, let me know. I really did enjoy giving it and I hope I can tweak it a bit and give it to another group soon in the future.
You can find my slides at http://slidesha.re/1qqCc1L
I also have a set of links I will try to post here as well.
Hello again from SharePoint land!
It’s been a while since we talked about KB2775353 and how it made our SharePoint 2010 servers where I work extremely sad and kept them from correctly displaying our BI dashboards in 2010 (see here).
I was originally told when I found this bug that the fix would be put into a patch around the August 2013 CU timeframe, and sure enough with the newest round of patches released I went and got my grubby little hands on it. It took a few days for us to properly test it here, but I can confirm from our internal testing here that this patch corrects our display issue with our dashboards! Yay!!!!
Just to be clear, this is my personal scenario of how things went, YMMV.
We originally patched our farm to the April 2013 CU for SharePoint Server 2010 due to an incorrectly applied patch that came in from windows update, so we were originally forced to move to the April 2013 CU. For the meantime we have been working around this issue by displaying our dashboard items in a different way. We notified MS support of our issue and verified it was indeed a bug and they went to work on correcting it.
So when the August 2013 CU for SP2010 came out a few days ago, I had a couple of options on how to bring my farm up to the latest patch level. What I ended up doing was patching my farm with SP2 and then after checking to make sure everything applied correctly from this patch, applied the August 2013 CU for 2010.
After this, we had to redeploy our dashboards back to how they were before the April 2013 CU mess and verified that everything looks good and is back to normal.
Now I can put all of this mess behind me and work towards upgrading everything to SharePoint 2013. I hope this helps anyone else who runs across this scenario with their BI setup in SharePoint 2010.
Thanks for all the twitter questions and replies to my previous post everyone! I think with 2013, I will be more conservative in my patching going forward…
Have you ever had a workflow, form, or process in SharePoint Foundations 2010 that needs to reference user account info like email address, job title, or other info that needs to stay up to date?
In our setup we have many electronic forms that our users complete to request things, update things, or to ask to be approved by someone. However, if they get married, or change jobs, or some other life altering event happens, then we need to make sure that AD and SharePoint Foundations are in sync. The very first time they log into SharePoint Foundations it grabs this info and puts it into a user information list that is hidden and referenced. You can read more about this here by Tobias Zimmergren (@zimmergren). He does a great job of explaining where this is located and what it does.
Our problems came about when users changed job titles or email addresses because this info only gets added when the users first logs on and never gets updated again. <Insert sad trombone noise here>
So my buddy JP (@flagship50) took it upon himself to write a tool called the Foundation User Profile Service (or FUPS as I like to call it). It solves our problem quite nicely and keep all the pertinent information that we need for our users synced with what is entered into Active Directory.
Next we created a place for it on CodePlex so the entire world could enjoy it. Give it a once over and see if you like it. It has worked great for us so far and he is working on a 2013 version for those of you who are curious.
I thought I would take this opportunity to let everyone know about a bug that was discovered by our BI team this week with the April 2013 CU for SharePoint 2010.
The bug is mainly affecting PerformancePoint Services in SharePoint 2010 Server.
Background: Our users have a set of KPI’s that are published on a couple of dashboards that contain operational data. Normally when the dashboards load, these graphs, charts, and reports are hidden to improve initial loading performance. When the user clicks on the proper cell for each KPI, the dashboard will create 1-3 graphs, charts, reports or a mash up of the 3 to display further details.
Issue: We noticed earlier this week in our environment that when we would click on a cell for a KPI, none of the charts, graphs, or reports for that KPI would display properly. It was just like they weren’t being displayed when the user clicked on a cell. Our users have many important reports they get to by this process, so this affects us in a big way.
One odd thing to note that we found in our troubleshooting of this issue is that if you edit the page in SharePoint that each dashboard is on, the graphs and charts and reports show up just fine. When you stop editing the page in SharePoint, the dashboards go back to not showing them. Weird, huh!!??
Workaround: For now the only workaround we have for this issue is to display all of our charts and graphs and reports on the dashboards at the same time. This does slow down our performance a bit, but this is better than the users just not being able to see the information they need at all.
As we learn more about this, I will update this post.