Love them or hate em, like them or not, it can’t be ignored that Microsoft has been making some big splashes lately. We've started to reflect on how the software giant has been putting out some pretty cool stuff that truly improves someone’s daily life or job. Let us share some Microsoft tech that impresses us. Read this blog to get the list.
If you’ve worked anywhere and had a cubicle in the last 15 years, you likely use Outlook to get and send email. Even though we all use Outlook, there are features (some new, some not) that if you take the time, can help your day to day be a LITTLE easier. I’m not saying this features will make you coffee or solve world peace, but every bit helps right? Let’s look at 8 great features in the latest iteration of Outlook (2013).
When it comes to Visio's high quality, yet static content, can we make that flat data more interactive and fresh? Sure, with Data Graphics! Some people refer to drawings like this as having data-behind. You might have seen the Supply Chain example from Microsoft in a number of demos, and think that it must be some overly complicated configuration. It’s not!
Generally the out of the box provided ID column is used as the “Issue ID” since it auto-increments by default. Invariably, users need to be notified whenever issues are created or updated, so they subscribe to alerts on the list. When they get their notification email, they notice that the Issue ID is missing, so they aren’t sure exactly which issue got updated.
We can fix this by adding the ID field to the email alert file. Let's take a look how.
The purpose of this article is to try and compile a list of features removed or discounted features, not list all of the changes or improvements in SharePoint 2013. This list will vary somewhat depending if we’re talking SharePoint on-premise or SharePoint online, but I’ll try to call out the differences where applicable.
Let's say you’re a member of a sales team and you need the ability for your sales peers and managers on your team to be able to see your contacts. Did you know you can use SharePoint to store and share Outlook contacts? This blog will show you just how easy this is to do!
How do users communicate their SharePoint frustrations, feedback, and questions? If the answer is “they send an email” or “they open a helpdesk ticket” then this is for you! We have created a solution for SharePoint 2010 on-premise and SharePoint 2013 on-premise and Office 365 that provides a powerful yet simple mechanism for users to provide feedback. Best of all, it's free!
After getting a client's SharePoint available on the public interweb and thus available to CRM, we installed and activated the list component. But when we went to an Opportunity or other entity that was configured for document management, it would throw an error...
In this post with PowerShell, I wanted to show you how you can write a script that will enable versions but starting from a subsite instead of the entire site collection.
See if this sounds familiar:
Someone asks you “Can I get an email reminder for these events on the team calendar?”. You think well, we can set alerts, so you go look into the alert settings, so you go look into the alert settings, and quickly realize that alerts don’t work like that. The alert mechanism in SharePoint will send the alert subscriber an email based on an action happening on the item (it is being created, edited, etc). We need the trigger to be based on a date. So what to do?
As a SharePoint solution architect, when I’m not creating site columns and configuring SharePoint server databases, I'm meeting and talking to clients about their business requirements for collaboration technology like SharePoint. On a project basis like assessing a clients desire to upgrade their SharePoint environment, this involves documenting a SharePoint environment or a lot of times just business processes. There are many tools available for these types of drawings, and one I typically use for drawing SharePoint farms and topologies is Visio.
Welcome back to to my series on the basics of SharePoint. If you've already read the first post, we covered what SharePoint is. Now we're ready to dive into how to create content in SharePoint. (Notice I said create content, not any form of structure.) We have to crawl before we can walk, right? Then we can move on for the super users on how to create structure, the things that hold the content.
I was working with a client recently in a simplified signup site. In effect what was needed was to make the fields read only based on the role of the user. Follow me as I walk you through the steps using only SharePoint Designer, no code or InfoPath required!
As part of an auction site I was working on for a client, one part of the solution was to use an InfoPath form for users to submit their bids. This post focused on how to get the dynamic images from a SharePoint Picture library.
When working with SharePoint, you occasionally need to work with related data. Since SharePoint isn’t setup for true relational data, that means we’re typically working with lookup columns from a child to a parent list. This is all fine well and good, but I had a client ask me for some special filtering and output with this related data. After reviewing my options, I found that the quickest way to do this (in under 15 minutes) is to use Microsoft’s Power Pivot add-in for Excel. No SharePoint Designer required! If you have Excel 2010, you will need to download and install the add-in. If you use Excel 2013, the add-in is already installed, you just have to enable it.
Whether you are using SharePoint 2010 or SharePoint 2013, it is very likely you are taking advantage of the Managed Metadata service for taxonomy and other purposes. Hopefully you have a development / test environment in addition to production, and if so you know it’s a struggle to keep them in sync. If your groups, term sets and terms are not identical down to GUIDs between the two environments, if you move a database from one to the other then all your terms will be broken… not good.
The point of this blog is not help you sync your environments with metadata. Let's dive in.
After having some pleasant discussions in the SharePoint Yammer SPYam community on this subject and finding almost no information online about this topic, I thought I’d put some fingers to keys and do my part to share some information. This post assumes you have basic concepts and knowledge of SharePoint taxonomies, but review TechNet if you need more info or to get up to speed on the basic concepts.
While working on a client request recently, I came across a way to easily work with date and time values in a SharePoint Designer 2010 workflow. I was able to solve this using only SharePoint Designer. I reviewed other solutions, and I will give links to a couple others in case they are needed. This worked for me, and I didn’t see anyone else with this exact solution so I thought I would share for the greater good.
While working on a PowerShell script to do some updating list items in SharePoint, I first had to get some properties from the user account in Active Directory. The end goal was to update a managed metadata field, choosing terms based on the root OU that the user resided in Active Directory. I found an easier way to do this with PowerShell and wanted to share.
If you’ve gotten to this page, it’s because you or your users make heavy use of SharePoint lists, and the inevitable request came up “Ok this is great, but I can’t print this item, help!”. Like most things with SharePoint, there is no one right answer (sometimes there is!), but some are definitely easier than others or better depending on your needs. I'll show you a couple different common solutions out there in one place, and what worked for me.
A client contacted me the other day about some help with printing a picture library. I found a simple way to do this, and I wanted to share to hopefully save someone some grief.
I've seen folks all over the interweb and even a client of mine hit this issue, so I wanted to take a moment in this blog to document it for posterity. It deals with the Usage logging features of SharePoint, and the all too familiar Microsoft bugs.
In this post I wanted to share a resolution to an issue I had with a client recently. At first I thought this was going to be a difficult issue, but as luck would have it the resolution was amazingly simple if you know what to look for.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.