OneDrive Integration Into Your Blogs

I just figured out something cool. I was reading http://thebitsthatbyte.com/ because I met the blog’s author, Kelly Rusk, at SharePoint Saturday Charlotte over the weekend and wanted to check on some stuff he had mentioned. He pointed out in a recent post that one could use intellisense in OneDrive if you go to open up certain file types. I checked by creating a .js file. The built-in text editor is pretty darn good. Then I spotted something else that drove me to make my own post. Inside of a folder in OneDrive, there is an embed link you can hit. It gives you code to insert on any other page to show people the contents of that folder. Here is the folder I’m going to dedicate to all of the big files for this blog. Check it out folks.

See that? You don’t even need to authenticate because it passes a key along with the link.

PSA: InfoPath and Office 2016

Office 2016 was just released today. I was so excited to download and install it. I have my reasons. Just ask those of you who get annoying junk mail notifications in Outlook 2013 how much you hate it. Yeah, Microsoft never fixed it.

I then started looking into how I should upgrade. Most easily done if you have an Office 365 subscription. Ok, cool. I then noticed that the InfoPath icon wasn’t included among the apps. We all know by now that InfoPath has been deprecated. I thought that maybe Microsoft would include the 2013 version with their 2016 suite, since they wouldn’t be upgrading it.

The answer is NO. If you have Office 2013 suite install with InfoPath 2013, that version of InfoPath will get wiped and removed along with your entire Office 2013 suite and upgraded to 2016. In order to create/modify InfoPath forms on Office 2016, you will need to reinstall InfoPath 2013. This will leave you with two “installations” of Office: 2016 and 2013.

Just a friendly PSA. Check here for more info.

Hidden Titles

The primary purpose for me to start this blog was to highlight a few of those war stories I’ve got of saving the day. I will leave the names of the clients I’ve had out of this.

 

So here is a rather recent event. A whole lot of us were on a rather large contract, and the client failed to get paperwork completed on time to keep us on site. We were sent home on mandatory vacation. While on vacation, I learned that there might not be funding for my position after we got back. I spent the time looking for another position. Anyway, three weeks pass and we finally get back to work. A few days later, a guy asks me why he can’t see Title on one of his libraries. After looking at that library for a minute, then others on the same site, then all the way to the Title site column of the whole site collection. Yes, you may have guessed it, Title had been set to hidden and cascaded through the whole site collection.

 

Now, in a happy world, I’d just run to the farm admin and ask him to restore from a backup, but that wasn’t going to be possible. It happened a week after we left the client’s site. It was another three weeks before I learned of this, so all of the documents that had been edited and pages that had been modified would have been lost if we restored from the last good backup. The only other contractor working on SharePoint with me spent seven days going to every single list and library in the site collection, converted all of them to manage content types, and set Title to required, optional, or hidden as required. I spent only two days on the task before I started to work on my last project before leaving to start with a new company.

 

Lessons Learned

  1. Obviously, never screw with the out of the box (OOTB) site columns.
  2. Don’t let qualified people have full control permissions at the root of a site collection. For the record, I had previously stated the one responsible should not have permissions there, but I’m only a contractor.
  3. Your farm admin should have a list of daily tasks and weekly tasks. Somewhere among them should include a series of tests to check for changes via the audit log. You can never expect communication to work properly even if you think you have a good change management process in place, so you need to have someone checking these logs often.
  4. Don’t expect a lot of love from the ones who enabled the person who did this when you fix it. This was a very public airing of dirty laundry. Just do your job and take notes.

SharePoint Irony

I do find it kind of ironic that this blog is not SharePoint hosted (no pun intended, Scott). Blame Microsoft. They can never seem to figure out what they want to do, so I guess this ended up here on WordPress.

If you would have asked me what SharePoint was 4-5 years ago, my honest answer would have been “a Microsoft product”. One two-day crash course and five clients later, I’m thankful to have been able to make a comfortable living developing in SharePoint exclusively. A lot of this is owed to great SharePoint gurus like Scott himself, who was my co-worker and is my colleague.

SharePoint is a great platform for business process automation. It is not a dumping ground for documents (but you can use it for that if you want). SharePoint can be your friend, and it can be your worst nightmare. It is what you make of it. In application, don’t think of things in a SharePoint-ey way, think of it practically. Then, learn and apply SharePoint to fit that practicality.

Oh, and one more thing Scott. It’s spelled “Tardar Sauce“.

Why SharePointSuperHeroes

Firstly, I wanted to explore a few war stories and tell you about those SharePoint challenges I’ve faced over the years.  I hope to bring on a couple others to share their experiences as well.  I’ve maintained madwhitehatter.com for the last few years, but that was a blog using Office365, which has stopped allowing new public-facing sites.  It was also a domain to cover far more than just SharePoint; it was mainly aimed at hacking and security.  That was the goal nyway.

Secondly, I’m making a new start with a new company.  As a farewell gift, my coworker gave me the coolest picture ever.  She grabbed a little bit of everything about me and had an artist put it all into one graphic that says a lot about who I am.

Scott is the SharePoint Super Hero
Scott is the SharePoint Super Hero
Most of the clients I’ve had over the last several years were tied to the Army and I was in the Army for 10 years. I’m kind of grumpy, like Tartar Sauce (the coolest cat to grace the internet). Lastly, when someone needs help, I’m the hero.

Honestly, I know a lot of people in this business who are far smarter than I am, especially when it comes to adding code to a page to render data better or change the UI/UX; but, I’ve often been the only one for them to come to their aid. I have been in the customer service business my whole life, not just in IT. The truth is that we all are in the customer service business whether we like to admit it or not. Taking the time and patience with the customers, whether you can solve their issue right then or not, goes a long way. You also need to genuinely give a damn, and I do. It isn’t just a job.