I’m thrilled and humbled to have had the opportunity to be a guest blogger over on Microsoft’s Humans of IT (HoIT) blog. My post is about balancing all our obligations, embracing imperfection, and leaving room for joy in our endeavors.
It can be difficult to keep up with all the messages in LinkedIn that come in from colleagues, old friends, recruiters, and bots. Even if you have every intention of replying at a later time, your message buddy can see that you’ve seen their message but chose not to reply immediately. This can add false tension or anxiety to the communication, or just send a signal to the other party that’s unintended such as how you might value that person or their objective. Your message buddy can also tell when you’re typing and may be anxiously awaiting what you have to say even if you change your mind and delete the draft, leaving them hanging.
Let’s reduce some stress and disable read receipts and typing indicators so you can reply when you’re able with the peace of mind that no unintended feelings were conveyed when skimming between meetings. Just keep in mind that if you do this others won’t see that you’ve read their message or a typing indicator when you type AND you won’t be able to see the same from anybody else. Disabling it from applying to you removes your ability to benefit from it applying to others.
How to disable typing indicators and read receipts in LinkedIn messages
By default your LinkedIn profile may appear in public search results and individuals who aren’t logged in to LinkedIn can see some of your information (depending on the privacy settings of each component as you added it to your profile). This public/anonymous access is also what allows Outlook to find your profile as a potential match for you if you haven’t connected your profile yet.
In this post we’ll go through the steps to disable your public profile so that only logged in users may connect with you and/or view your profile in whole or part depending on your settings. You can also watch a video demonstration at the bottom of this first section below.
How to disable your LinkedIn public profile from anonymous access
Mark Rackley recently tweeted about the ability to create a calculated column in SharePoint online document libraries that would automatically render thumbnails for documents. In the GIF from his tweet, it shows how this works for media files.
Naturally curious, I had to see how this worked for documents of .docx, .pdf, .pptx, etc. types. What I found is that it only currently supports some file types:
Supported file types (there’s likely even more I didn’t test):
Images (.png, .gif, .jpg, etc.)
Not-yet-supported file types:
Create a thumbnail column in SharePoint Online document libraries
1. Add a new column to your document library (library settings > Create column).
2. Set the column name to Thumbnail. As for type, you have two options:
Leave type as Single line of text. Thanks to Dario Cassinerio for sharing that Single line of text type works as well as (and more simply than) Calculated set to [Title].
In this age of building bots and eliminating needless clicks and such to get employees the info they need faster and more directly, we need all the best practices we can find when creating solutions for users. This post will share a better practice when it comes to getting reliable, fast results from SharePoint lists and libraries that don’t rely on search index configuration or endless view sprawl.
If you’re just here for the quick answer, here it is. For string values, you can simply add this to the end of the list’s URL to filter it as specified.
Spaces in field names and values: If your value includes spaces, replace them with %20.
[IntFieldName]: Internal field names (like Client in the example below is actually the original Title column) can be found in List Settings > Column Settings > Select Column > Check URL of column settings page (it contains the internal field name following &Field=).
If you want to learn about how this came up in my work and why I chose it as a solution, read on.
Recently, I was involved in troubleshooting a bot that would search a SharePoint list using its built-in search box. However, the bot would be searching for items that were created minutes prior and the search index hadn’t updated yet so no results would be found and the bot would fail to complete.
So I suggested we filter instead of search.
Filtering lists works independently of the search index. Meaning I can create a new item in a SharePoint Server 2019 (or any SharePoint version) list right now and then filter the list and find that new item immediately. But if I search immediately, it won’t be found yet.
Want to argue about continuous crawls as workaround? Send your thoughts to firstname.lastname@example.org.
Changes to the process
For this particular bot, we’d be replacing this process:
Navigate to SharePoint list URL
Activate list’s search box
Enter/type search term (unique item identifier guaranteed to return one result)
with this one:
Create a variable for the search term
Navigate to SharePoint list URL with added URL parameter including variable from step 1 (taking us directly to the single result we needed)
It not only simplifies the steps involved, but reduces the likelihood that changes to UI elements will break our bot along the way.
Potential use cases
Sending workflow emails with direct links to lists and libraries already filtered
Reducing the number of views on a list by having users bookmark URLs including the filter parameters the view would have
Improving bot reliability by eliminating some UI-dependent steps
Eliminating search indexing delays for users or bots searching for new items
I had an issue come up today where a user wanted to search a SharePoint list by the default ID column.
Problem: The ID column cannot be indexed and is not searchable using just the ID number itself.
Solution: You can still search ID numbers in lists if you include the proper Keyword Query Language (KQL) syntax. Format your search as ListItemID:3 (replacing 3 with your own ID number, of course) and it will work.
And yes, this works in both modern and classic list search experiences and in SharePoint Server and SharePoint Online/O365.