Category Archives: General

InfoPath, “Save A Snapshot”, and PDF print truncation

I ran into an interesting issue today with printing an InfoPath form. A customer reported a problem where her PDF printout was getting truncated off the right side of the page. She was using the File > Info option, and then using the Save As Snapshot to generate the PDF file. The resulting PDF file ran off the side of the page, and there was no InfoPath or Adobe PDF setting that I could find to fix the issue. Strangely, when I had her print directly to an Adobe PDF print driver, it worked fine…


After some brainstorming with the help desk, we discovered the underlying issue. In Windows 7, I’m running my text size at 125% instead of 100%. I was having the same issue as the customer. When I switched back to 100%, the printout was perfect.

So… if you end up with the same issue, I hope this saves you some time searching around InfoPath or Adobe. Just check the text size setting in your operating system.

I struggle with being a SharePoint “developer”…

This is one of those posts that I have to write, as it’s how I deal with things I’m feeling. In this particular case, it’s how I feel about being labeled a SharePoint “developer”. It sort of bubbled up inside me as I was reading various reactions to yesterday’s announcements during the Future Of SharePoint event.

When I hear someone use the word “programmer” or “developer”, I think (as do probably most people) of someone slinging code and spending all day in a IDE like Visual Studio. These are the people who integrate one thing with another using all sorts of code frameworks and protocols. And to be certain, they are worth their weight in gold (provided you can actually talk with them as a normal human being).

But there’s another world of “development” that is where I live. It’s the skillset of taking existing parts of the system (I like using the term “out of the box”) and wiring them together to create solutions for a customer and organization. Yes, a power user could do this, but the vast majority of people who use SharePoint don’t want (or don’t have the skills or mindset) to do that. They want to have someone who understands the software and their issues wire all that up for them. They want a quick solution that’s easy to use, and they don’t give a rat’s a** what is happening behind the scenes. They just want results.

And that’s what I deliver… quick solutions that meet a business need and add value to the organization.

So what’s wrong with that? Well, I’ve technically been a programmer my entire 35+ years in IT. I’ve done time in the COBOL world. I’ve created RPG III programs. I coded rather cool LotusScript agents in Notes. But realistically, I’ve always been the type of developer you could put in front of the business, and that was focused on a solution that could be implemented quickly. But compared to the people I naturally compare myself to (the hardcore developers), I’m pretty much worthless. Or at least that’s what I beat myself up with…

In yesterday’s Future Of SharePoint webcast, I saw a LOT of things that will make a huge difference to how my customers will be able to work. I saw a LOT of things that will be fun to play with, and to hook up to create new solutions. Based on the reactions from others, they saw the same things I did. But there was a number of people who pretty much didn’t care for anything that was announced. In their opinion, it was either not enough or was focused in the wrong area. They didn’t show real code. They were “consumerizing” SharePoint and destroying the abilities of ISVs to add value.

It seemed like most of those people were what I’d consider “real developers.” And so I wonder… am I just not good enough to understand why I shouldn’t be excited? Am I wrong for not being up in arms about the direction of things? Am I following a path that is a dead-end?

Once I pull myself out of that mental spiral, here’s what I come up with…

I’m not an IT Pro, in that I’m not the person who knows all the networking/configuration/etc that comes as being an admin. I’m probably not a “programmer”, in that I don’t sling real code much. I *am* a developer, in that I develop solutions for my organization that make a major difference and add value. I also serve as a SharePoint Help Desk, a technical consultant to the business, a training and adoption driver, and I wear whatever hat is necessary to keep SharePoint (and soon to be Office 365) running and my customers happy.

None of this is an excuse to not learn new skills. That’s a whole different list of things that I beat myself up over on a regular basis. I am a charter member of Imposter Syndrome Anonymous, and I don’t think that will ever go away until I retire or die. I often wonder if I’d be able to find a new job if I had to leave this one for some reason.

But having said all that… I deliver value. I build things. I’m open to being labeled whatever reflects that, whether developer, programmer, engineer, or internal consultant. I’m pragmatic, in that I’m sure there are a number of “flaws” in SharePoint and Office 365 that should be addressed. But I’m excited about where things are at, I’m excited about the direction that Microsoft is going, and I’m excited that I get to play in that sandbox.

And with that, I’ll head back to my happy world of making others happy. It’s how I roll…

Did you know that Visio can check your site for broken links?

This is one of those features I stumbled across a number of years ago, and it still seems to be a very well-kept secret. You can use the Web Site Map diagram to tell Visio what site to map out. Visio will also X-out every page image where the link is broken.

For more information, check out

I know there are probably site crawlers and link checkers that are more comprehensive and have more whistles and bells to play with. But it’s hard to argue with a tool you may well already have sitting on your desktop.

Slides from SharePoint Saturday Redmond – Leading Your SharePoint Customers To Water… *and* Teaching Them How To Drink

Here are my slides from SharePoint Saturday Portlandia on November 14th, 2015. We had a good turnout, and I made it through the session even though I was nursing a cold.

I think the most enjoyable part of this is the discussions afterwards. I love how this content sparks ideas and the “I could do that” statements.


Slides from SharePoint Saturday Boise – Leading Your SharePoint Customers To Water… *and* Teaching Them How To Drink

Sandra Mahan and I presented this session at SharePoint Saturday Boise on October 3rd, 2015.


Do you pick your technology, or does your technology pick you?

This is one of those topics that I’ve been close to, both from an observation perspective as well as my own career.

As a “technology person”, people expect you to know everything (or learn it quickly). It’s possible to be aware of a large number of technologies but most people end up concentrating on a few specific areas that pay their bills. There are rare people that seem to pick up everything, but I’m not that person. The question for most IT people is… what technology do I focus on, and when should I decide to learn something new (or drop something that I already know/work with on a regular basis)?

It seems like there are two scenarios that play out in my mind. If you’re a consultant, you’re always trying to ride the bleeding edge of what’s in demand and what will keep you employed. If you’re working as a regular employee, you’re focused on working with whatever technology keeps you employed.

I’m going to step back into my Notes world as an example… mainly because I went through this. As a Notes developer, it was my job to make sure I knew as much as possible about Notes development. That could mean just Notes client development, but it also included web development as well as XPages as the Notes environment evolved. It used to be you could focus on Formula language and sort of ignore LotusScript. Then it was needing to know LotusScript but XPages was still a nice to have. Now it seems you have to know XPages, and client development is sinking quickly as an in-demand skill.

As a regular employee in an organization using Notes, I focused mainly on Notes client development, as we had a lot of that. When I found myself unemployed and headed into the consulting/contracting world, I found that I wished I knew more about web development, portals, XPages, etc. When I was able to get re-employed by my original company, I was back in my sweet spot of client development again.

While I would have been happy to continue to do that and push those limits, life had different ideas. We moved from Notes to SharePoint, and now SharePoint is my primary focus. Much like Notes, saying you’re a SharePoint developer can been a variety of things… out-of-the-box development, SharePoint Designer workflows, JavaScript web development, C# coding, etc.

To the point of my title… I could take a step back, decide that I think Hadoop, big data, and Python are where it’s at, and start planning my post-SharePoint technology life. I could also look at all the options available to me in the SharePoint and Office 365 world, and push myself within the arena that I’m already familiar with.

I think it’s important to keep an eye open to where IT trends are going, but no one has a crystal ball. Telling someone they need to leave their current technology may make sense from the outside looking in, but sometimes that technology picked you given where you’re at and the opportunities that are available.

Keep your eyes and your mind open to where things are going, and take a realistic look at the future of your organizational choices and your personal career. Then decide… do you need to pick your technology, or are you OK with the fact that your technology picked you?

Don’t always assume things are what you believe them to be…

I had one of those “duh” moments today…

I had a report from a customer who was claiming that a link to a document in an automated email was broken. Since the email was generated from an InfoPath form when the form was submitted (and presumably saved also), I had my doubts. However, when I went to the library and checked for the document, it wasn’t there. No recycle bin, the submitter had Contribute access without delete…

… or so it appeared.

It turns out that the person submitting the form is one of two people who share the same name. I saw “her name” in the permission list, and assumed all was well. But when I finally noticed her picture compared to an email picture, I noticed they were two completely different people. The person who was submitting the form didn’t have Contribute access, so the email would send but the form wouldn’t save.

Note to self… never assume that everything is as you believe it to be without double-checking the obvious.

Post-Ignite thoughts and reflections…

I’ve been home for about 24 hours after a great week at Microsoft’s Ignite conference in Chicago. For those who don’t know (or know me more from my IBM/Lotus world), Ignite is like Lotusphere on steroids. It’s not just SharePoint content… it included SharePoint, Office 365, Exchange, SQL Server, and a number of other technologies. One-stop conference experience for everything Microsoft…

In my opinion, Ignite was perfect for what I wanted and needed (yes, those are two different things). My current role is as a SharePoint developer/designer/no-code solution resource for my company. I’m the type of person who deals directly with the business, translates their needs into solutions without them having to be technical experts, and answers the questions they have on a daily basis. I needed this conference to both teach me new things and connect me with people who do that same type of work. I got a lot of that all week long, and I have a lot of new material to sort through and new things to learn.

However, there was something much more important that happened. Between sessions, talking with colleagues, and brainstorming with Sandra Mahan (aka my SharePointBuddy), I now understand that Office 365/SharePoint 2013/SharePoint 2016 isn’t simply a technology choice or decision. Watching what Graph/Delve does to connect people with information (findability and discoverability) really does change the way that people can do their jobs and leverage what they know.

Yes, I did drink the kool-aid…

I was a big believer in what Notes/Domino could do for an organization. I did the whole evangelist “Lotus is good/Microsoft is evil” thing. But as my technical world started to change focus to SharePoint, I shifted to more of a view of “it’s just technology to build solutions.” I don’t get into detailed arguments over what is right and wrong with technology X. I just focus on what I *can* do with it (mostly out of the box) and what I can do for my business customers. This has served me well for a (very long) number of years, and it’s certainly less stressful.

The bad side of that shift was that I lost that “something special” that I used to have. I’m still good at what I do, but I tend to react and do instead of thinking ahead and leading. I get too bogged down in being busy (and productive) instead of being effective and leading. I stepped away from the IBM/Lotus community where I wrote, blogged, spoke, and co-authored. The problem is… I really enjoyed that. I enjoyed helping people, being on stage, knowing who was who and who did what. I loved traveling to conferences (often on my own dime) and presenting in user group settings that changed the way our community viewed tech conferences. I got a lot of personal satisfaction helping others take their first step in the conference community, co-presenting with them when they first stepped on stage, and then watching them go on to speak internationally.

This week at Ignite has “re-ignited” that passion that’s been buried for far too long (sorry, I had to use that pun). Microsoft has a vision for the workplace that makes sense to me, and they’re doing things that are coming together nicely. I’m excited to see how this plays out, and there is plenty of opportunity at my place of work to make incredible things happen. I meet the people who are part of this community, and I’m excited to be part of that. I want to start pushing myself again, and passing along those things to others. And to top it off, I get to work with incredibly talented people on a daily basis, and we are going to make some awesome stuff happen.

Back in 1997, I sat among 10000 people at the Lotusphere Opening General Session, totally overwhelmed by the music, the videos, the lasers, and the buzz of the crowd. I had no idea what I was doing, but I said to myself “this is what I want to be good at… this is what I want to be an expert in.”

It’s time for that to play out again, starting now.

The “Cannot filter more than 10000 rows” error in Excel is misleading…

A recent help desk case took me longer to resolve than I expected, mostly because what the error message said and what I thought it was saying were two different things. A customer called about a spreadsheet that was being generated by SSRS, and they were thinking they weren’t seeing all the data due to Excel showing an error saying it couldn’t filter more than 10000 rows. I’ll admit I was a bit concerned, because this spreadsheet would *always* have more than 10000 rows, so what’s the problem?

I found my answer here:

That message refers not to the number of rows displayed in the spreadsheet, but the number of items that appear in the column filter dropdown. For instance, you’ll see all 28000 rows in the spreadsheet, but you see that 10000 rows message when you click on the dropdown for the filter:


That 10000 refer to the number of entries you would see under the (Select All) line of the checkboxes. It simply means that you would not be able to see all 28000 items in that filter list, but you’d still see all the rows of data in the spreadsheet.

A better example would be the dropdown for one of the date/time fields:


If the filter list just had YYYY/MM/DD, you would have maybe 1000 unique dates over the last three years. But since it goes down to HH:MM:SS, close to every one of the 28000 rows has a unique date/time combination. The filter can’t show all those unique values, so you get the error message. You could still use the filtering to find all 2014 items for January through May, but you couldn’t drill down to also refine the filter to the exact times because you couldn’t show and expand all those combinations.

Basically… all the data is there. Nothing to worry about…

Tip For Using OneNote To Manage Professional Reading

I have a really bad habit of “collecting” links to really interesting articles tweets, emails, and other stuff I want to read for my professional life. But unfortunately, I find it far too easy to get behind in the list, and pretty soon, it’s just a collection of things I’ve never read.

Time to put OneNote into play…

Taking a tip from Sandra Mahan, I’ve started putting the links into daily reading pages with To Do tags. The goal is to spend time reading at least five articles a day (I have to read a bit more than that to clean up my lists). As I cover my items and check them off, I not only keep myself more current on the latest SharePoint news, but I also have a history of things I’ve read if I ever want to track them down later for reference.

Today I got my Twitter Favorites/To Read list transferred over to OneNote pages. I’m working on email newsletters, and I also have to clean out my Pocket saves that are work-related. There are a number of entries that need to make it out there also.


What I like about this method (in addition to the tracking and responsibility that’s built-in) is that I can have this list anywhere I go. It’s on my home computer, on my iPhone/iPad, and my work machine. Whenever I have a few moments, I can pick off one or two reading items and I know that will be updated throughout all my devices.

OneNote rocks, and I continue to find great uses for this tool…