If you’re using a document Name field in a workflow but it’s not working as expected, it could be because there are apostrophes () or ampersands (&) in document names. In this case, SharePoint evaluates apostrophes () to &#39semicolon and ampersands (&) to &ampsemicolon As you can see here, most other punctuation evaluates perfectly well:

cats

Note: This problem only occurs when using apostrophes and ampersands in document names, in document libraries. And we can fix the issue without needing to rename the files.

Document names cannot contain these punctuation marks: \ / . : * # “

Regular lists and document library fields aside from the Name field shouldn’t experience this issue. But if you’re using & or in your file names, and calling those file names in workflow, here’s how we can make it work:

Advertisements

Outcome:

process

docoutcome

Intro:

Look at that workflow above – have you ever seen something so beautifully simple? I’m excited to share several solutions with you in this one post. This post should cover the following:

  1. Working with content types
  2. Creating a template for each content type capable of having merge fields
  3. Finding a way to merge list item info into a new document via workflow
  4. And if you’re super ambitious, expanding the workflow just a bit with an if/then statement to use different templates based on conditions in your list

But because this is a massive topic and could be tailored an infinite number of ways, I encourage you to comment or tweet me for additional guidance more specific to your scenario. So here we go!

Outcome:overlaysbeforeafter.PNGIntro:

So you’ve made a SharePoint calendar. In fact, you’ve even made some different views for it and then made those views into overlays. Hoorah!

But now, looking at the finished product, the unevenness of the overlay links leaves something to be desired. This post will show you how to take your overlays and, in just a few minutes, turn them into a more polished look as seen above.