Yes, you can have a BCC field in your SharePoint Designer workflow emails. I didn’t know this until recently, and was pleasantly surprised. It’s quick and simple, so let’s get started.
Note: You can do this in both 2010 and 2013 SharePoint Designer workflows, using the exact same steps.
Perhaps you, like me, built an exciting Microsoft Flow workflow and let it go into the wild without much additional thought. But at some point, you drop a lookup column into the mix and your Flow stops working. It tells you the field is not supported in query, even if that specific field isn’t being utilized in the Flow. I believe this has something to do with REST, but we won’t dwell on the cause – let’s get to the workaround.
The scenario I’ll be using is my cross-site publishing alternative using Microsoft Flow where I’m basically copying data from list items in one site collection to create new list items in a different site collection. This is helpful when someone does some sort of data entry once, and other people are then entering much of the exact same data. This copies all of the overlapping data to a new list item for the second site collection to reduce duplication of work.
It sounds simple but with a lookup column in the destination list we get the error. For this I’ll be using SharePoint Designer and Microsoft Flow (of course) in combination, though you could certainly try it all in Microsoft Flow. I just find parts of the process simpler in SPD. And while your origin data may be different (MailChimp, Twitter, etc.), and your exact scenario may differ, this workaround should still have value in concept.
This is a popular request that I’ve recently modified, thanks to the recommendation of a colleague, to be responsive to different device or browser sizes. By default, SharePoint lists respond to their viewer’s size but once customized with a fixed pixel width will lose that feature. This solution utilizes percentages so you can create column widths ideal for any screen.
In a recent post, I discussed hyperlinking URL title text and adding tooltips. I used the above screenshot which also illustrates what we’ll accomplish in this post which is to remove the select/deselect checkmark column, column headers, toolbar edit/new options and chrome border. This leaves us with a simple title and list. Pick and choose what you’d like to remove for your specific needs, and let me know if you run into any issues.
Let’s put those link lists to good use. I wanted one master or parent link list with a number of views. I would then use those views in different list view web parts across my site, removing the toolbar (view/edit/add options), column headers, chrome border and select/deselect checkmark column so that essentially I had a section of my page with a header/chrome title like “HR Forms” (removing default link to “parent” list) and then just a list of hyperlinked form titles with tooltips providing more info on each form as seen above. This post will cover how to get the hyperlinked title text with tooltip. Another post coming soon will cover the “clean-up” of the list view web part so that you’re left with a title and list items alone.
Here’s how to quickly correct the issue behind the server error: version of SharePoint Designer
When doing an if/then statement within SharePoint Designer involving a people column, our only options are “equals” or “not equals.” If you want to be able to use “is empty,” “is not empty,” “contains,” etc. this article will show you how to get around this limitation without any scripting. We’ll basically be creating a workflow variable to use in place of the original column.
If you’ve created a dashboard and have multiple list view web parts that you’ve connected to one another so that they share parameters or filters, then you may be familiar with this default double arrow icon:
You may have even found it to be located at _layouts/images/rbunsel.gif or _layouts/images/rbsel.gif (depending on whether it’s the “selected” or “unselected” icon).
And now you’re ready to replace it with something a little more fashionable. I recommend installing an icon package (free) on your site so that you can use icons from the set throughout your site to continue customizing various out of the box, and quite ordinary, icons. In this post, we’ll use FontAwesome. Check out their amazing set of icons at http://fontawesome.io/icons/ and even try searching for “open” or “expand” to see some good alternatives to the less-than-perfect double arrow default. For this example, let’s use fa-search-plus.
Ready to step up your icon game? Me too.
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:
- Working with content types
- Creating a template for each content type capable of having merge fields
- Finding a way to merge list item info into a new document via workflow
- 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!