The Document ID service is great but limited. Engineers tend to want more metadata in their IDs!
Using PowerApps to work around the limitation of only being able to embed Power BI dashboards in modern SharePoint pages
Recently I came across an excellent blog post from Jethro Seghers that covered getting started with Office 365 PowerShell Automation. In the post Jethro walks through the process of setting up Visual Studio Code to work with Visual Studio Services. The process uses Git as the broker. The end result is that your scripts can be stored in a secure source repository. In following the post I learned several lessons that I thought I'd share
The moral here is if you change the number of columns in a file you need to update the Source definition in Power BI
Quick post: geolocating your data in Power BI
For me Ignite 2017, is the conference where sub-sites died. The sub-site is dead, long live the site.
For me the Search announcements made at Ignite 2017 are probably the biggest ones that they made at Ignite as they are the ones that really effect an end users experience. An effective and efficient search is fundamental to their productivity.
Yammer’s Roadmap session at Ignite 2017 demonstrated that the product team had listened to their MVP’s and customers. This my take on how they should deliver the roadmap.
It’s quick and easy to add Yammer feeds into Microsoft Teams using Yammer Embed.
As part of our drive to Groups and Teams we need to modernize our existing templates. For this work I have been working on a definition of modernity for SharePoint sites