We are drowning in Office 365 news and we love it!! We share some of our favorites in this episode. This time we are recording using Teams because Christina is on vacation at the Canary Islands and I am in Stockholm. Pretty good sound quality anyway. Thank you for listening. Cheers!
Save list or library as template
Many times when you setup a document library (or a list) with lots of metadata columns, views, etc you want to save it as a template so that you can reuse that model on all other sites without having to do the same setup over and over. But if you go to the Settings of a modern site in SharePoint online you will not find a link to “Save list or library as template” anymore. As an on prem user, you are used to work like this, using templates to be able to setup a list or library quickly somewhere else and that will save you lots of work since you don’t have to recreate the same columns/views etc again. Here are two options to achieve this in SharePoint online:
Option 1: Using Powershell
To enable the “save as template” option you must run a Powershell command. I tried this and it works just fine: you will see the link in the library settings and if you go to “Add an app” your list template will show up as we are used to. Note: you must go to “add an app” because in modern views, if you click on “New” and “Document library” you will not see the list of templates.
When things like this are removed or hidden in SharePoint online, it is of course for a reason, but I cannot tell or judge if it’s a risk to enable this link using the PS command. Maybe someone who reads this knows? Then please leave a comment, it would be much appreciated! It has worked fine in my tenant and the libraries that I added using my template works exactly the same as any other modern library. But I can only say: run this at your own “risk” 🙂
The following cmdlet must be run on the site where the library is that you want to save as template, and then also on the other sites where you want to use the template. So you are not enabling the command on your entire tenant. Open SharePoint online management shell and run the following cmdlet:
Option 2: Using Content Type Hub
In this episode we discuss and use some of the latest news that has been released to Office365 recently. We also talk SharePoint swag, or rather, the lack of it! Don’t you agree? 😉 Contact us on firstname.lastname@example.org or on Instagram where we are @witgirlspod or on Twitter @sharepointbabe and @bananisen. Thank you for listening! Cheers from Lise & Christina
Just a short news flash:
If you are a Spotify user, then you can listen to our podcast there now!
We have followed Ignite from Stockholm of course and discuss some of the news (there were so many this year!) around SharePoint, OneDrive and Teams and some more… We need an extra show about the news only! You can watch all the on-demand sessions at https://myignite.techcommunity.microsoft.com/videos.
Lise has worked as an extra for two different tv-shows and one of them will go up on Netflix next March, we will post more info on that then! ?
We are very proud to announce that we have our own theme music now and it’s made by Mikael Wejsflog, THANK YOU so much for this, we love it!!! You can hear the full track on our Soundcloud page on https://soundcloud.com/user-61240900.
If you like our podcast, please rate us in iTunes, we would be so happy!
Thank you for listening!
Cheers from Lise (@sharepointbabe) and Christina (@bananisen) and we are @witgirlspod on Instagram.
I was asked by Jens Weil, one of the organisers this year, to be a reporter at the SharePoint Saturday Conference that was held in Stockholm on 1 September 2018. Of course I said yes! It is always fun to meet people from this community!
I still think it’s good though for on-prem customers who don’t have PowerApps available.
I built a form that I needed to validate before the user press “Submit” and the validation is to check if mandatory fields has a value. So simply put: check for empty strings before Submit. I tried using Rules but you can only have up to 5 conditions, and I have 8 fields that must be checked. So that did not cover all fields of the form. Here is a screen shot of all fields in the form that are mandatory:
So how do you validate if fields are empty on a web enabled form?
You can not use the Validation rules that are built in, because they will only work when you fill in the form in InfoPath client. But, we can check if the field has any text in it.
I added a text field that I called “AllEmptyFields”, that will be hidden on the form. And in that field I added the following formula:
string-length(YourFieldName) * string-length(YourNextFieldName) * … add all the fields you want to check!
So what you are doing is counting if there are any strings inside the field, and if they don’t it gets the value 0. Now add all the fields that you want to check, and separate them by the * sign. Which means that this field will default have the value 0 and then, when you have filled in all fields in the form, it will calculate a number that simply counts and sums all the characters in those fields. (The screen shot shows the formula in Swedish – sorry. But you get the point, right?)
Then on the Submit button you add a Formatting rule. The rule is to hide the Submit button if the calculated field “AllEmptyFields” contains 0:
If “AllEmptyFields” = 0 then Hide the control (and the control in this case is the Submit button):
Now when I fill in the form, the Submit button will not be visible until all mandatory fields are filled in! Very nice and no risk of empty forms being submitted.
Are you using modern team sites or communication sites in SharePoint online? Then there are some good news for you when it comes to changing the look on them. Some of the news are easy to change in the UI and others you must use PnP Powershell to enable.
Change the theme on a modern site
There is a new setting called “Change the look” on the wheel menu.
This will open a pane where you can choose what theme you want for your site. If you don’t see a list of different themes, then the tenant Administrator might have prevented users from changing themes. Read more here. Select a theme:
When you select the theme a new link “Customize” will appear that let’s you do further customizations. The “Header emphasis” controls the background color of the site header. Default it is set to “None”:
Change the header of a site
Here are screen shots of how the different header emphasis looks like:
Change the look on a hub site
If you have a hub site then you can change the theme and all the connected sites will inherit the same theme.
Change the look on a classic site
You have the same option “Change the look” on classic sites, but then you come to this old familiar page:
Mega Menu – is it coming or just a rumour??
This is something that I have read about but not been able to activate on my sites. Not sure it has been released yet, or if it’s just a rumour… Or I just don’t know how to enable it 🙂 Anyway, when you enable levels in the navigation then you get that “fly-out” effect, which is annoying because if you click outside it the menu disappears:
I would like to use the mega menu instead to make the menu larger, more informative and easier to use. Now there’s supposed to be a PnP cmdlet (you cannot do this in the UI) called MegaMenuEnabled that you can set to True or False, that should control if you want to enable or disable a mega menu. But when I run that in PnP PowerShell I get the following error “The property ‘MegaMenuEnabled’ cannot be found on this object. Verify that the property exists and can be set”:
No luck finding it on this command either: Get-Command -Module *PnP*
Guess I have to be patient, not my strongest side though! I will update this post after Microsoft Ignite, maybe that is something that will be launched there! Exciting!