Skip Ribbon Commands
Skip to main content
Microsoft MVP
 
Home
SharePoint for Non-Developers
 

 Posts

 
January 21
Dynamic Excel Web Part

In all versions of SharePoint and Office 365, the Excel Web Access web part has been around for years.  It is part of the enterprise version of these products.  Web part connections can be created on pages in SharePoint, to send information between web parts. 

The requirement in this scenario is that a department has a bunch of spreadsheets in a document library. They are all similar, and the end users would like to be able to quickly flip between them while staying on the same page. 

This can be done with an Excel Web Access web part and the library on a web part page, using web part connections!  Here’s how:

What you already have:  A document library with a bunch of spreadsheets in them.  In my example, they are all exactly the same, just with different data in them. The tables, charts and named ranges are all exactly the same.  My library is called “Spreadsheets”.

  1. Create a web part page for this new dashboard.  A quick way to do this is to go to your “Site Pages” library, and in the Files tab, click the New Document drop-down, and choose Web Part Page.
  2. Give the web part page a name, double check that it’s being saved into the Site Pages library (or you can put it somewhere else, just pay attention to where it’s going), and click Create.
  3. On your new page, click the Edit Page button in the ribbon, and then click the Left column zone to Add a Web Part
  4. Add your library-full-of-spreadsheets, mine is called Spreadsheets.
    image
  5. On this same page, click Add a Web Part in the Right or middle column zone, and in the Business Data category, choose the Excel Web Access web part.
    image
  6. With the page in Edit mode again, click the little drop-down box at the top right of the Excel Web Access Web Part, and choose Connections –> Get Workbook URL From –> Spreadsheets (or whatever the name of *your* library is)
    image
  7. On the Configure Connection screen, choose Document URL, and click Finish.
    image
  8. Now stop editing, or save the page.  By default, the web part will show the first spreadsheet in the library, according to whatever order your data is sorted in that web part.  As you click the little gray double-arrow next to each spreadsheet, the web part on the right changes to show that spreadsheet!

image

In mine, I even have multiple named ranges and tables, so I can let the end user use that little drop-down at the top right of the Excel Web Access web part (that says AllProducts) to switch over to different parts of the spreadsheet!

1/23 update:  On SharePoint Power Hour this week, I did a demonstration of this solution.  Click to watch the video.

image

January 19
Speaking at SPTechCon in Austin 2015

125x125This February is going to be exciting, as this is the first time that the SharePoint Technology conference (SPTechCon) is happening in Austin, Texas!  I’ll be presenting four sessions there, and here’s the info about them.  You can also get $200 off by using ROGERS as your registration code!

Feb_9

1:30pm - 2:45pm

Making the Most of the Out-Of-Box Web Parts

There are over 50 out-of-the-box web parts in the enterprise version of SharePoint! In this class, you will learn just how flexible and useful these Web parts are. Not only will you get a detailed look at the Filter, Excel, Social, Rollup and Media Web parts, but you will learn about a few new ones in SharePoint 2013 such as the Content Search Web Part. You will then learn how to customize some of these Web parts, see examples, demonstrations, and learn about new features. All of this is done without writing any code. Push SharePoint as far as you can using out-of-box functionality! This class is a mixture of 2010 and new 2013 Web parts.

Level: Intermediate; Audience: Information Worker Essentials


3:45pm - 5:00pm

Driving User Adoption, From a Technical Standpoint

Lori Gowin & Laura Rogers

When IT professionals set up the infrastructure of SharePoint, the subsequent task of end user adoption is often left to the business unit. During this process, the business unit will often turn to “The SharePoint Person” for help and guidance. Good news, IT Pros, there are useful technical configurations in the administration console to improve and increase user adoption. Ultimately this will improve user satisfaction with SharePoint and increase productivity. The instructors both began as SharePoint Administrators 11 years ago. The real world experience of implementing these practices will be integral in this class. Among the topics covered will be defining user audiences, improving Office integration with SharePoint, and demonstrations of improving how users can quickly and easily get to the information they need. When leaving this class, you will possess a specific action list that may be used to optimize their technical experience and drive user adoption.

Level: Intermediate; Audience: IT Pro Essentials


Feb_10

10:00 – 10:45

Panel Discussion


11:30am - 12:45pm

Creating an Approval Workflow, Part 1

Forms and documents are everywhere in your organization, and a lot of them must go through an approval process. SharePoint is such a flexible platform, it provides us with multiple methods that can be used to build our processes. In this class, learn about these different out-of-box ways to create a workflow around a form approval process. You will see the various alternatives when creating an approval workflow: content approval, out of box workflows, and the task process designer in a SharePoint Designer workflow. Quickly create and implement intuitive workflows for your critical IT and business systems, with no programming involved! The concepts in this class are applicable to both SharePoint 2010 and 2013. This is part one of a two-part presentation. This first part has only the simple and purely out-of-box settings and functionalities, geared toward beginners.

Level: Overview; Audience: Architecture Essentials


2:00pm - 3:15pm

Creating an Approval Workflow, Part II

Forms and documents are everywhere in your organization, and a lot of them must go through an approval process. SharePoint is such a flexible platform, it provides us with multiple methods that can be used to build our processes. Quickly create and implement intuitive workflows for your critical IT and business systems, with no programming involved! In this advanced class, learn about creating a completely custom new hire approval process. In this part two class, we will build out an HR onboarding workflow in SharePoint Designer, using a complex example that involves a process with both serial and parallel components, with multiple workflows. The concepts in this class are applicable to both SharePoint 2010 and 2013. This is part two of a two-part presentation.  This second part has only advanced concepts geared towards those who are already familiar with SharePoint Designer workflows, and does not contain any of the out-of-box workflow options taught in part one.

Level: Advanced; Audience: Architecture Essentials

January 12
SPChat on 1/15–Automating Business Processes

This Thursday, 1/15 on the SharePoint-Community site, I will be doing a SP Chat!  The topic will be automating business processes in SharePoint and Office 365.  The way it works is that the chat room is opened up for anyone to ask questions, and I answer them by typing my responses in the chat window in the order that they arrive.  Come check it out and sign up here:

SharePointChatPromoMasterLa

1/19 update: This has ended, but you can view the transcript here.

January 07
Working with Video Content in SharePoint 2013

I wrote this article back in 2012, for SD Times, and thought I’d go ahead and post it here also.  This also applies to Office 365, and Office 365 has a video portal feature as well.

In the SharePoint 2013 Preview and in the Office 365 Preview, there are some great hidden gems when it comes to working with video content. In this article, you will learn about adding and managing video content, and several ways to display that content on pages in SharePoint.

Where do I put my videos in SharePoint?

The first step is to create an asset library. From there, videos can be uploaded to the library just as you would add documents to a document library. Some interesting things happen behind the scenes each time a video is uploaded. Each video gets its own special page that displays more information about the video, as well as associated content. This screenshot shows a video called “Content Search” that has been uploaded, and the properties of it are displayed on the page as well.

image

How do I manage the properties of the video page?

After a video has been uploaded, click on the name of the video in the library, and then go to the Manage tab. Here are the important things to notice:


Edit Properties – The coolest thing on this screen (to me) is the ability to capture a video thumbnail right out of the video. The owner field defaults to the name of the person who uploaded the video, but it can be changed. There are also some checkboxes to indicate whether you want users to have the option of downloading your video or grabbing the embed code for it. You can also select the names of the people who are shown in the video.

Permissions – Decide whom you want to share this video with, if it needs to be different than the permissions for the library itself.

Manage Video Renditions – This setting is great because it allows accommodation for end users who may be on slower network connections. Different versions of the video with different bitrates may be uploaded here. When watching the video, end users will see a graph-like icon on the video that will let them switch between renditions.

Here is a screenshot of part of the Edit Properties screen:

image

Related items – Another cool new feature that you may have noticed in the first screenshot is the ability to include related items. For example, if my content search video has a Word document or two associated with it, those documents can be added as related content. Since each video has its own document set in here, those documents are contained within its document set.

Web Parts

Everything in this article so far has been confined to the library itself. What about situations where videos need to be displayed in Web Parts on other pages in the site? There are a couple of out-of-the-box Web Parts that are great at this:

Media Web Part – This Web Part has been around since SharePoint 2010. Simply add it to a page, then use the Media tab at the top to configure its properties, such as the video to look at and whether to play it automatically. This Web Part has been around since SharePoint 2010. Simply add it to a page, then use the Media tab at the top to configure its properties, such as the video to look at and whether to play it automatically.

Video as page content – Also, on publishing pages and wiki pages, media content can directly be inserted into content areas, and the configuration of the media itself is the same. When editing these types of pages, the Insert tab will contain an option for video. You can navigate to your SharePoint content, or use the embed code for any video from SharePoint or the Internet.

Content Search Web Part – This is a new Web Part in SharePoint 2013, along with a whole category of Web Parts called Search-Driven Content. Video content can be displayed in this Web Part, and there is a Web-Part setting called Control, which has a setting called Slideshow. Videos can be displayed in this slideshow style so that they can be scrolled through in a pretty graphical interface. This screenshot is of a Content Search Web Part on the home page, which shows one video at a time and has two total videos:

image

Video as page content – Also, on publishing pages and wiki pages, media content can directly be inserted into content areas, and the configuration of the media itself is the same. When editing these types of pages, the Insert tab will contain an option for video. You can navigate to your SharePoint content, or use the embed code for any video from SharePoint or the Internet.

November 21
Office 365: Information Rights Management

Information Rights Management is being rolled out to Office 365 right now.  I read about it here, and decided to go into my tenant and try it out.  This is very exciting!  What is Information Rights Management?  The quick explanation is that it lets you have tighter control over what happens to your files (mostly just MS Office files) once they have been emailed out or downloaded to people’s computers.  You can define things like whether they are allowed to print it, or even set the content to expire after a certain date.  This is not a new thing, but it’s always been something out of reach and very expensive, and now I see that it exists right there in my (Office 365 Enterprise E3) tenant!!!!

I tried it out today, and wanted to share with you the steps I went through to turn it on.  You need to be an Office 365 admin to be able to do this.

  1. In Office 365, at the top right, click the Gear or the Admin button and go to Office 365 Admin.
  2. Expand Service Settings on the left, and click Rights Management.
    image
  3. Click Manage.
  4. On the left it will say Rights Management is not activated.  Click the Activate button.  Do you want to activate Rights Management, click Activate.
    image
  5. Back at your Office 365 admin center, expand the Admin section on the left, and choose SharePoint.
  6. In your SharePoint admin center, click Settings on the left.
    image
  7. Scroll down to the Information Rights Management section, and choose Use the IRM service specified in your configuration.  Click Refresh IRM Settings.  Scroll down and click OK.  This won’t work if you haven’t done all the previous steps.  I know, because this is the part that I tried first.  Winking smile
    image
  8. Now go to the library in SharePoint that you would like to protect with Information Rights Management.  (note that this is something completely different than an information management policy).  Go to the Library Settings page.
  9. Click Information Rights Management.
    image
  10. Check the box to restrict permissions on this library on download.  Give it a name and description.
    image
  11. Click the Show Options link in gray.  THIS IS AWESOME.  This stuff only applies to the file when people open it in the client software, and has nothing to do with what can be done with the file if they’re looking at it in the browser. 
    image
  12. You can read all about these additional settings here:  Apply Information Rights Management to a list or library.  Notice that under the Configure document access rights, I left a bunch of boxes unchecked.  This only applies to people who only have SharePoint permissions to read or view these files.  I don’t want them to be able to print it, and I don’t even want them to be able to type in it at all.  Click OK.
  13. I logged in as a user who only has read permissions to this library.  Notice that when I click the File menu, the options such as Save, Save As, and Print are grayed out:
    image
    Also, when I try to type in the file, simply nothing happens.  This is so cool, people as for this type of thing ALL the time!  Oh, and by the way, when using IRM, apparently there is no more option to edit the file in the browser using Office Web Apps.

Here are some reference links:

Using Azure Rights Management: http://technet.microsoft.com/library/en-us/jj585006

Office 365 trust center: http://trust.office365.com/

November 14
Panel: InfoPath is a Dead End

In October, at SPTechCon, Andrew Connell got several of us together to have a panel discussion on the topic of forms, for the Microsoft Cloud Show podcast.  The title is Episode 49 - SPTechCon Panel Recap - InfoPath Is a Dead End: What Form Should Your Forms Take?

We discussed the fact that InfoPath is eventually going away in the year 2023, and what we should do with our business forms.

The hosts were:

» Andrew Connell (@andrewconnell)

» Chris Johnson (@loungeflyz)

The panelists were:

» Lori Gowin (@lorigowin)

» Mark Rackley (@mrackley)

» Me

» Jennifer Roth (@jennifermason)

Click to listen to the recording:

logo

Technorati Tags: ,,
November 10
SharePoint & Office 365: Cross-site Content Concepts

I recently had a call with a customer who had a pretty common requirement. Their content editors work on files on a team site, and they want to have a way to have that content exist on the team site and on their main intranet site as well. Currently the content editors are making the changes in two different places, and they want to streamline this process for efficiency's sake. They do not want to have to give everyone in the company access to the files where they are being worked on in the team site, and they are hesitant about allowing these content editors to actually edit the intranet site itself.

How can this be accomplished in SharePoint 2013 and Office 365? There are several different options available, with varying degrees of setup complexity, which I will describe in this article, with associated resource links for each.

SharePoint Content Deployment feature

This is a feature that you can activate. You would have a content site collection which is where users author files, and then the target site collection where you want the content deployed to. Out of the box, this is pretty limited in that it will deploy an entire site collection or all the sites under a certain site collection. This is a job that you would schedule to run at certain times. Content Deployment also entails quite a bit of configuration on the server side by your server administrator. Depending on your method of authentication and whether you have HTTPS, this can be fairly complicated. As far as the end users are concerned, they are editing and working on content in one location, and it automatically gets pushed to the other location at the interval you've determined. This is a great blog post that I came across that describes the process including an approval portion in the middle. This feature is not available in Office 365. Most of the content on Microsoft's site and on blogs is written for SharePoint 2010, because in 2013, cross-site publishing is a new feature for achieving this same type of result.

http://www.denisstadler.com/sharepoint-2010/sharepoint-2010-publishing-feature/a-simple-web-content-management-how-to-authoring-approval-publishing/

Cross-site publishing

The concept of cross-site publishing allows you to have an authoring site collection and a target site collection just like content deployment. Unlike content deployment, a great functionality is that it utilizes your managed metadata structure. The people who are authoring content are adding items to a simple list and categorizing them. In the target site collection, navigation is automatically generated based on your managed metadata structure, and the items that the authors wrote will end up displaying on the page of whichever category that they assigned that item. One negative that jumps out at me is that although this feature makes heavy use of the Content Search web part which is awesome, this web part has limited out-of-box display choices. You would almost definitely need to elicit the help of a branding person in order to get that content to display in a pretty way. You can deem a list or library where you author content as a catalog, and then define what field you are going to use to categorize each item in that list or library. This feature makes it nice and simple for the content authors, because they just to a list of there their announcements or articles are, whatever the content is, enter their data, and as long as they categorize it correctly, it will display in the right place in the target site collection. They don't ever have to edit actual pages in a page library. Benjamin Niaulin wrote a great post which simplifies this whole process and walks you through setting up some simple cross-site publishing for company announcements. http://en.share-gate.com/blog/migrate-sharepoint-2013-what-is-product-catalog

This is a great post letting you know when to use content deployment versus cross-site publishing: http://blogs.technet.com/b/tothesharepoint/archive/2013/07/23/3585007.aspx

 

The Content Organizer

As we go through each of these options, they exponentially easier to use and set up. The content organizer is a great way to automatically route documents based on conditions and rules that you set up. This is another way to allow people to author content and not necessarily directly edit the location where the content will end up where it is consumed by the content readers. Unfortunately, content organizer rules cannot apply to pages in a page library, though. They cannot be used for list items, either. The content has to be a file in a library. Another negative is that there isn't really a good way to see what's been happening, from a reporting standpoint. There's no way to look at a library and be able to tell which files have been sent to that other location, especially if they're just sending a copy. If you had a large number of files, you'd end up having to somehow compare the set of files in the source location to the files that are in the destination location.

There are a three main ways these content organizer rules can be used:

  1. Users can have a single drop-off location where they upload or save documents, and then from there, documents automatically get sorted and placed in the correct library and folder according to metadata and the rules you've defined.
  2. Users can use a custom send to location which will appear on the Files tab in the ribbon when a document is selected. This Send To drop-down box will give them options as to where they would like to send the file, such as an archive or an intranet site where the content could be read by a broader audience. When these Send To locations are defined on the server, the administrator chooses one of three actions for that file. The options are to Copy, Move, or Move and leave a link.
  3. Information management policies can be created, which will automatically move files to the destination location based on a certain date field. For example, when the date of the last file modification plus one year arrives, the file could automatically be moved to an archive location.

Here are some reference links on the content organizer:

http://office.microsoft.com/en-us/sharepoint-server-help/configure-the-content-organizer-to-route-documents-HA102772938.aspx

https://www.youtube.com/watch?v=JLNVwhy7JiU&index=33&list=PLkxSkUuLZ3fTmkn0BP8L0nPtSz3TzETl0

 

Custom "Send To" Location

The custom send to location is similar to #2 in the content organizer rules above, but even easier. Also, it does not require access to Central Administration or even Site Settings to get it configured. This is functionality that you can set up that allows one library one specific location to send a copy of files to. This only exists for files in a library, and not list items. When the user selects to send a file to this location, they are prompted to choose whether they want the original file author to be prompted to send future updates to the copy of the file, each time it is checked in. They also have the option to allow it to create an alert on that document so that they will know when it changes and potentially needs to have an update sent out to the copy. An example use case of this would be an HR department that has a library on their private team site where they collaborate on documents. They also have an intranet site that everyone in the company can read content. When a file is ready to go public, they would use this Send To location.

After the copy has been sent, the original file location will have a button in the Files tab of the ribbon called Manage Copies, so that they can see a list of where current copies of that file are, and send out updates if needed. The destination location even has a column called Copy Source, where you can view the URL of the location where the file came from.

 

Publishing Pages Approval

With the simple goal being that the content authors shouldn't have to author or update identical content in multiple places, there's good old publishing page approval and out-of-box workflows that could be used. When you create a publishing site, one of the templates is Publishing Site with Workflow (hint for sub-site: choose Use unique permissions in order for it to work correctly). Using this type of site for publishing allows you to have a strict process in place around the editing and publishing of content on the intranet pages.

Again, with this original requirement at the top, how could this functionality be used to accomplish what they want? Content editors would be able to directly edit pages on the intranet site, but when they do this, each page would have to go through an approval workflow before the changes could be approved to go "public". But what about the fact that they need to be able to get to this content from their team site as well? The Content Search web part is very powerful. One of the things it allows us to do, is display content from one place in your farm… in another place in the farm. The content from the library on the intranet site could be displayed in a web part on the team site. They're editing it in one place, the intranet site, but they can get to it from a couple of places. If they did the opposite, if they only edited the files on the private collaboration site and tried to display them on the intranet site, they would have to give everyone in the company access to that library's content on their private site. This was not an option.

 

As you can see, there are many different options, with varying pros and cons. There are several factors to consider when deciding which route to go. Some factors are: What is the content we're dealing with? Items? Pages? Library files? Can content editors be allowed to work on the intranet pages directly? What is the quantity of content we're dealing with? Does there need to be visibility into which content has been published, by whom and when? To get started, I definitely recommend testing out each of these options, and experiencing them from the content author perspective and the end user (content reader) perspective, in order to make an informed decision.

September 26
Microsoft’s Next Big Conference

Back in July, Microsoft announced that there will be one big unified technology event for enterprises, and it is going to be held in May in Chicago.  This conference is supposed to replace several different conferences that you may have been to before:

  • SharePoint Conference / Office 365
  • MS TechEd
  • Exchange Conference (MEC)
  • Lync Conference
  • Project Conference
  • Microsoft Management Summit (MMS)

Earlier this week, I had an amazing opportunity.  Microsoft invited me and several other community influencers to Chicago to talk about ideas for this new conference.  They included influencers and MVPs who have been to one or more of the aforementioned conferences, as well as about ten Microsoft folks.  We all arrived on Sunday, and had meetings Monday and Tuesday.

First, we took a bus to the event WP_20140922_012 (640x361)location, McCormick Place.  We got a tour of the venue, and then we went to a meeting room and went straight to work.  Here is a photo of my SharePoint friend, Naomi Moneypenny, and I looking at an event being set up in one of the expo halls.

What did we do in our meetings?  Basically, Microsoft asked us a *bunch* of questions.  They want to make this conference the best it can be, so they took a lot of notes on the ideas and brainstorming that went on.  They asked us questions like:

  • What has been something about a previous conference that you liked and would like to see return at this new conference?
  • What new ideas do you have about things you may have never seen at a conference and would like to see?
  • What makes a conference “cool”?
  • What kind of session builder / content is important to you?
  • For someone who has never been to a Microsoft conference, what would be some driving factors that would bring them in?
  • SOCIAL – we had a lot of discussions / ideas about how to involve people socially, bringing in ideas of things that went well in the past, and trying to get people engaged who wouldn’t normally be.

That first evening, we all went out to dinner and then went to the John Hancock Observatory, AKA 360 Chicago.  We got to do the Tilt, and then had a nice little reception and dessert.  Here are a couple of pictures from that:

WP_20140922_028 (361x640)WP_20140922_032 (640x361)

Images_untitled

The next day, Tuesday, we had more roundtable discussions, and we did some photo and video shoots as well.  My crappy little camera phone doesn’t really do it justice, but Rick Claus took a ton of pictures with a really nice camera.  Who were the other participants and influencers?  Let’s see, I’m just going to list them by twitter name here, you know, since we’re all so social…

@NickLagalante @Begley_D @joeysnow @RicksterCDN @Golnaz89 @MichaelBender @Pluralsight_Ed @fabianwilliams @nmoneypenny @meetdux @ToddKlindt @_JoeKelly_ @expta @Ladewig @Hoorge  @JasonSherry @tompacyk @larryla @Hfitz11 @MarkDeFalco @olafhubel

Sorry if I’m missing anyone.  I just grabbed these out of my twitter stream/mentions from those days.  In counting the people in the above photo, I’m clearly missing some names.  Winking smile

Anyway, so what next?  Microsoft is going to continue to keep us engaged, and updated.  They encouraged us to tweet and blog about this roundtable.  Also, you can use the comments area here on my blog if you have any input around any of the topics / questions that I mentioned above.  I’ll be sure to send your feedback right to Microsoft! (my blog comments are moderated, of course)

There were so many amazing ideas and super smart people, that I could go on and on, but in general THANKS MICROSOFT for wanting our feedback, and I’m excited to see what comes out of all of this.

10/22 update: Microsoft announced the name of the new conference last week! Microsoft Ignite! Registration is open!

Msf-Ignite-FB-600x600-orange

11/24 Update!  Call for topics!  This is a survey.  Microsoft is asking ALL OF US what content we want at this conference.  Please make your voice heard here.

See you there!!

September 11
SharePoint Conditional Formatting

In SharePoint 2013 and Office 365, there is no more design view in SharePoint Designer, and of course InfoPath is slowly being depreciated between now and 2023.  Without these tools, how do we go about creating business solutions easily like we have been doing for years?  I’m not a programmer, and I know that most of my audience here… you’re not programmers either.  Well, there’s this thing called JSLink that was introduced in SharePoint 2013.  It is another tool we can use to create fairly simple conditional formatting and lots of other formatting on our forms and views… except it entails JavaScript.  Some of it is so simple that even *I* can do it.  I found a ton of blog posts  where developers (a lot even friends of mine) have been blogging about cool capabilities and tricks for a couple of years now.  The thing is, the people who read these blogs are also developers, so that’s who they’re tailored to.  Most of them don’t bother stating the basics like “what is a JS file and where do I put it?”, because their readers already know this stuff.

In this post, I will show you, the non-developers how to use JS Link, and some extreme basics about how it works.  Once you are armed with this knowledge and you want to research it further, you will better be able to translate what the developers are writing and maybe be able to use it. 

Here we go, and remember that I am not a programmer and I don’t know anything technical, I’m just figuring it out as I go.  This blog post was my inspiration. 

Okay, I’m going to use a super simple example here, because mostly what I’m demonstrating is not the script language and how to program, but how to get JSLink actually working in your environment.  Again, this is really cool to me, because it allows us to do conditional formatting in views and forms without the need for SharePoint Designer or InfoPath!  The example is a SharePoint list of patients in a hospital.  There is a column called “Progress Level”, and their level is either “Good” or “Bad”.  Very simple.  I want to show the good ones with green text and the bad ones in red.  Actually, in order to demonstrate an image in conditional formatting versus a text color, the good ones will show in green text, and the bad ones will show a red icon, like this:

image

So here are the steps to do this:

  1. Create a custom list with a choice column in it called Progress.  Make the two choice options Good and Bad.  When you create this column, make sure you call it Progress, and you’re not just renaming some other column and calling it that.  This is important to making it work correctly.
  2. Insert this new list on your homepage or some page on your SharePoint site, as a web part, and make sure the Progress column is showing.
  3. Download this file to your computer.  It’s just a text file, but you’ll need to save it as a .JS file.  See, I removed the .TXT and changed the Save as type to All Files.
    PatientList.js

    image
  4. Download these image files to your computer:  RedGreen  Go to the root of your site collection, and to the default Library called Site Assets.  Upload these images to it.  The JavaScript file will reference that as the location of the indicator.
  5. If you have access to the root level of your site collection, go there and go to Site Settings.  In the Web Designer Galleries section, click Master Pages.  Then click the Display Templates folder. 
  6. In this library, go to the Files tab of the ribbon, click the Upload Document button, pick your JS file you downloaded in step 3, and choose Javascript Display Template as the content type when prompted to fill in metadata.  
  7. Here is what you are prompted with, and what to fill in, and click SAVE.
    image
  8. Here are what some of the settings mean:
    Target Control Type:
    View – a view in a list of multiple items
    Form – a form that users are filling out, such as dispform/editform/newform.
    Field – just a single field, although I can’t find any references that really explain what this one is for and when it would be used.

    Standalone: Every reference I’ve seen says to set this to Override, but no one says what the purpose of the other option (Standalone) would be.

    Target Scope: This is the URL relative to the site collection.  So here I put a / because I want this JS file to be available to use anywhere in the site collection.  If I only wanted to be able to use this code on a sub-site called “IT”, I would type /IT in this box.

    Target List Template ID:  The list in my example is a custom list (see step 1), and the code for a custom list is 100Here is a list of a bunch of other codes for the other list types.  Scroll down to the section called Type, to see the long list of codes.  I know it says 2010, but I can’t seem to find a list of updated codes for the latest version.  There are only one or two new list types in 2013, and the rest are going to be the same.

    If you’ve got your file uploaded now, you can skip to step 12.
  9. If you don’t see the JavaScript Display Template at step 4, or if you don’t have access to the root of the site collection, here are your different instructions instead of step 4.  Create a document library on your site, and name it whatever you want.  I’m just calling mine “Test Files”.  In the Library Settings, go to Advanced Settings, and change Allow management of content types to YES.
  10. On your library settings page, in the content types section, click Add from existing site content types.  Choose JavaScript Display Template, add it, and click OK.
    image
  11. Go to step 6.
  12. Anyway, now that your JS file has been uploaded, you’ll need the URL to it.  In the Files tab of the ribbon, click the View Properties button for this JS file you just uploaded.  Right click on the name of the file and click Copy Shortcut.
    image
  13. Now that you have the URL to the JS file, remember that web part from step two?  Go to that web part in the browser, and open the web part properties toolpane.  Expand the Miscellaneous section (more on that in my other post).  Paste your URL in the JS Link box.  Notice that when you save the web part, nothing magical happens.  Go back into the web part properties and notice that the URL is now showing as relative, like since my library is “Test”, it changed the URL to /Test/PatientList.js

    You need to put the ~site at the beginning, as shown here.  If your JS file were being stored in a library at the root of your site collection, and you were referencing it from web parts in sub-sites, you would use ~sitecollection instead.
    image

Now, save your page, and your web part looks like that that first screenshot (at least the progress column does).  At step two, I instructed you to put your list on a page as a web part, but if you want to you can just go to any regular view of your list, click the (Settings) gear at the top right and click Edit Page.  From there you can do step 13.

9/29 update:  I see some confusion out there around this last step of using the link to the JS file.  Please refer to a seperate blog post I wrote called SharePoint URL Basics.  This will help you understand how to obtain the link to your site.  In my example screenshot above, "Test" is a library in my site, and PatientList.js is a file in that library.

Wes Preston has a great blog, with a lot of posts about JS Link, and here’s a great “primer” that he wrote about it.  There are also hundreds of other blog posts out there about JS Link.

http://www.idubbs.com/blog/2012/js-link-for-sharepoint-2013-web-partsa-quick-functional-primer/

I’ll get into dissecting the syntax in another post.  In the meantime, feel free to dig in and see how the conditional formatting works, and browse the plethora of posts about it.

September 11
List View Web Part Properties

In SharePoint 2013 and Office 365, there are a couple of pretty useful new web part properties that I would like to point out.  When inserting an “app part” on a page (a list or library web part), there is a Miscellaneous section in the web part property toolpane.

  1. Insert a list or library (app) as a web part on a page in SharePoint.
  2. Open the web part properties toolpane.  (Select the web part and in the ribbon on the Web Part tab, click Web Part Properties)image
  3. Expand the section called Miscellaneous.

Disable view selector menu

This option is checked by default.  When unchecked, will show the names of the views in the web part.  When you click on the name of a view, it will navigate you over to that list or library.  So, even though you’re not staying within the context of whatever web part page you’re on, at least it will get you to another view of the list/library.

Disable ‘Save This View’ Button

This option is checked by default.  When unchecked, it will allow view modifications to be saved as a new view.  When a user is looking at a list or library in SharePoint, as soon as they start clicking column headings for sorting and filtering, the Save This View button appears.  I love this!  A lot of times, I’ll put a web part on a page, and use “edit the current view” a few times, to get it looking the way I want.  Then, if I want to do the same thing again, or on another page, I’d have to do that work again if I didn’t create it as a view in the first place.  This allows me to save my view and choose public or private and give it a name.  Keep in mind that this button will not appear until you click to sort or filter your columns.  Also note that as always, if an end user does not have permission to create public views, of course their only option will be to create a private view.

Display search box

The search box at the top of lists and libraries is awesome!  Now, this gives you the ability to display this small search box right in your web part, so users can quickly search through the files in that list/library and immediately see the results right in the web part without having to navigate away!

JS Link

Awesome functionality that entails JavaScript, so I’ll save that for another post.  Smile

Server Render

Takes away all of these checkboxes that I’ve described in this post, and removes any added functionality that they provide.

This is a web part with the view selector, save this view, and search box all showing:

image

Important note!  These settings only exist with the default style in your views.  In your view settings (not web part settings), if you have changed the style to anything but Default, none of these web part settings will be available to you.

image

I’ve recorded a video demonstrating all web part settings.  Click on the image below to jump straight to the part where I start talking about these Miscellaneous settings.

image

1 - 10Next
Migration tools for SharePointSharePoint CRMSharePoint CRMHarePoint Analytics for SharePointHarePoint Analytics for SharePointHarePoint Analytics for SharePointHarePoint Analytics for SharePointHarePoint Analytics for SharePointHarePoint Analytics for SharePointHarePoint Analytics for SharePoint40+ Premium Web Parts for SharePoint40+ Premium Web Parts for SharePoint40+ Premium Web Parts for SharePoint40+ Premium Web Parts for SharePoint40+ Premium Web Parts for SharePointSharePoint Mobile ExtensionsSharePoint Mobile ExtensionsSharePoint Mobile ExtensionsSharePoint Mobile ExtensionsSharePoint Mobile ExtensionsSharePoint Mobile ExtensionsHarePoint Analytics for SharePointHarePoint Analytics for SharePointHarePoint Analytics for SharePointHarePoint Analytics for SharePointHarePoint Analytics for SharePointHarePoint Analytics for SharePointHarePoint Analytics for SharePoint
Laura Rogers @WonderLaura
RSS FeedFacebookYouTube
 

 Pages

 
  
About Me
Data View Web Part Screencasts
Get My App
SharePoint FREE Resources
Speaking Engagements
Webcasts
 

 Our Books for End Users

 
  
  
Display a Sub-Site List on a Top Level Site128
Workflow: Reminder Before Due Date – MOSS vs. WSS123
InfoPath 2010 and Repeating Tables119
The Text Filter Web Part – Without Having To Filter Exact Text114
Displaying SharePoint Fields by Permission Level96
Web Part: Sites that I have access to87
InfoPath – Query Specific SharePoint List Data76
SharePoint List Form – Default User Information71
Using Content Types as Statuses68
List of SharePoint 2010 Web Parts68
Click to Copy List Item to New63
InfoPath 2010: Pre-populate the People Picker62
SharePoint 2013 Out of Box Web Parts50
Hack: Data View Web Parts in SharePoint 201344
User Information within InfoPath Forms44
1 - 15Next