With the new modern experience being pushed out more and more to the O365/M365 Admin consoles things are changing at a daily rate it feels like. The other day I was setting up some retention label policies and found things weren’t where they used to be. In order to help others, I thought it wouldn’t be a bad idea to publish the steps to publish a retention label in the new modern experience. This post assumes you already have a label created. If you need assistance with that please view my previous post on the steps for creating a retention or record-retention label.
I recently had the extreme pleasure of presenting at SharePoint Conference Twin Cities. This is a great one day conference with one of the largest user bases I have ever seen. I believe the total count of registrants was over 750 and over 400 attended! One of the sessions I presented was about how easy and efficiently you can integrate multiple systems with Power Apps and Power Automate (Microsoft Flow). Had a great room full of attendees with some great interaction. As promised I have uploaded the slide deck for this session so the attendees can have for themselves.
Thanks for coming to my session and thanks for reading!
In my previous post, I provided an overview of retention labels and their uses. In this post, I will demonstrate how admins or record managers can go about creating retention labels in Office 365.
Creating Retention Labels
- Log in to the tenant (https://admin.microsoft.com)
- In the left-hand menu click on Compliance
- The Microsoft 365 Compliance console will open.
- Open the Classification menu on the left-hand side and select Retention Labels
- Click on “+ Create a label”
- Enter the Top-Level information on your label:
- Name: Meaningful name to describe the label
- Description for Admins: Explanation of the purpose of the label. It contains any special information only viewable by admins in the console.
- Description for users: User-based explanation of the label purpose. May actually match the admin description.
- Click Next
- Enter the File plan descriptors. Note all fields are optional and only there to organize the labels within your organization.:
- Reference ID: Internal reference number for the label (you will likely need to click on the drop-down beside the reference ID and click on “Add a new file plan descriptor Id”.
- Business function/department: This is the department or functional group to which the label most closely belongs to. There is a list prepopulated, but if the department that best fits here does not exist you can add it by clicking on “Add a new file plan descriptor Business function/department”.
- Category: Select the category that best fits the top-level organization of the label. Like the other options, you can create a new one by clicking on “Add a new file plan descriptor category”
- Subcategory: like category above select the best category that fits the needs of the label. Not required. If a new one is required, click on “Add a new file plan descriptor subcategory”.
- Authority Type: Select the authority within the organization that requires the label. Can add a new one if required.
- Provision/citation: if the label is based on a documented industry standard. You can select from this list or create a new one.
- Click Next.
- Turn on Retention. If you leave this off, the label is not a retention label but a classification label only.
- Based on the requirements of the data retention, select the required amount of time the data should be retained. Have the option to retain forever or for a specific amount of time in days, months and years.
- For disposition, select Trigger a disposition review.
- Enter individual users who need to be notified AND have access to the disposition report. If they are not listed here they will not see the reports (even if Global Admin). At this point, you cannot add groups. This is coming through.
- Select the basis for when the data should be retained by. Options include:
- Select either “when it was created” or “when it was modified”
- Exchange only: the exchange mailbox can only be triggered on received or sent dates.
- If the document should be a record when the label is applied, click on the “Use label to classify content as a ‘Record’”.
- Click Next.
- Review the settings and once ready click “Create this label”.
In the next post, I will demonstrate how to publish this label.
Thanks for reading!
This spring I had the great privilege of speaking in front of a great room of people at SharePoint Saturday Montreal. At this conference i outlined how easy it was to build a great solution from conception to implementation using just PowerApps, Flow and a few connectors. In the space of half a session (I had to do some talking too ;-p ) I build a full solution using PowerApps, Flow, SharePoint and Azure Database. As promised here is the slide deck from my presentation.
Today I was trying to build a flow that kicked off from the Flow Launch Panel in my library. To do this for a list you simply need to create a flow based on the trigger “for selected item”. Once published the Flow Launch Panel is enabled on the list and you can now launch any flows that are attached to the list manually. You can do this for a library as well. The difference however is for a library you want to use “for selected file”. Seems really straight forward and easy right? Sure if it worked as expected.
Problem: Microsoft Flow Trigger “For Selected File” Missing
So here’s the problem. When you create a new flow a lot of people select the platform they are working with to decrease the count of the items to choose from. This one little step is what causes the problem. Allow me to illustrate. I created a new flow and wanted my trigger to be when a SharePoint file is selected in a library. So I created the flow, selected SharePoint and started to type “select” to filter the list. Here’s what I got:
Resolution: Easy, But a Workaround
The fix\workaround is so simple I hope Microsoft can fix it soon. To select the missing trigger, DON’T select SharePoint as the platform. When you start to type in your filter, it will actually show up before the “for selected item” trigger.
Thanks for reading!