It’s not easy to show a list (or part of a list) from one site collection on another. There are data view web parts you could try in SharePoint Designer, content search queries and page viewers in SharePoint web parts and then some scripting methods you could try, but I, in my enterprise environment, had no luck with those. This method, however, utilizes Microsoft Flow and works flawlessly. Here are a couple great features:
- Permissions are completely flexible. Set the “new” list to view only or whatever permissions you like while keeping tight control over the original. People will not be able to access the original list or site collection but they’ll see your up-to-date info you’re wanting to share.
- You can set this up so it’s a one-way publishing experience so updates on list 1 show on list 2, but updates on list 2 don’t show on list 1 OR you can set it up two-way so each list will update the other, creating a shared list experience without allowing permissions to access each other’s site collections
So let’s get started!
The new SharePoint framework has a lot to offer in the way of development possibilities and user-friendliness. Creating a page using their new default page experience seen above is much more intuitive, inherently mobile-friendly and easy to whip together some decent-looking dynamic content in just a few clicks. But this new experience doesn’t allow for adding web parts like you may be used to. And customizing layouts isn’t as accessible as it once was. The following few steps will allow you to create a page that utilizes familiar layouts (columns and sidebars) and web parts.
So you want your viewers to know the last time data was refreshed or updated in your SharePoint list without having the list’s default “modified” column repeating the same date hundreds of times and taking up horizontal space.
There are a number of solutions out there to show the date a list was last modified using code. This solution provides an option best used with lists you bulk update, or copy and paste to replace all data regularly, but requires no coding. It basically pulls out the “last modified” date of your first list item and displays it at the top as seen above. This solution is not for you if you are updating only specific items within a list.
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.
When using major and minor versioning, you could run into a situation where you wish to create major versions of all documents so that all are published and visible to all permission levels.
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.
Large lists carry with them a number of challenges, one being the ease of keeping everything straight when you’re thirty scrolls deep into a page. Sticky/floating headers are an excellent addition to your SharePoint lists that keep your headers at the top of your columns no matter where you’re at in the list for ease of viewing. This solution uses a script created by Daniel Stölzner of spoodoo.com and I’ve added a reference to jquery to simplify steps for those of you without jquery built into your master page.
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!