Visio
MSFlow is everywhere at MSIgnite including Visio
It will take me some time to review the content coming out at MSIgnite, but there is a re-occurring theme with the seemingly omni-presence of the Power Platform in all the user-facing applications that contain data. The Power Platform is PowerApps, Microsoft Flow, and Power BI ( view a session about this ) built on top of Azure. They work together, or separately, and they add an incredible amount of flexibility and democracy to applications. In the case of Visio, there is a tantalising view of what is coming shortly! Check out this video.
Visio Roadmap @ MSIgnite 2018
The first slot of the day at the furthest away room from the main conference area is not the ideal time to present anything, but those attendees that made it saw how many new features have been added to Visio recently, and what is soon to be added. The session recording should be available soon, but for those who can’t wait, here is a spoiler! ( View the session here )
My session @ MSIgnite about Visio and PowerBI
Well, that is the first day of MSIgnite over, and I am looking forward to hearing more about the roadmap for Visio today. I presented my session yesterday in a theater that seats 50 but 1,000 had registered for. In the end, the space was so full, I had no idea how many were there, but it was a lot! ( View my session on YouTube / View a 360 image)
I will be on the Visio booth now for a lot of the time during the conference, so please come talk to me about the possibilities of Visio solutions and integration with other Office applications and Office365. Microsoft have some cool demos of Visio / 3D Mixed Reality, Visio / MSFlow and, of course, Visio / PowerBI.
My book publishers have kindly provided some discounts for the duration of the conference:
- eBook Discount: 50%Code – MDVMP50
- Print Discount: 15%Code – MDVMP15
- Valid until September 30th 2018
- Go to packtpub.com
In addition, we will be offering the chance to win a copy of mine and Scott Helmers’ book “Microsoft Visio 2016 Step by Step” on the booth.
From Seattle to Orlando in 21 years
I was going through my wardrobe the other day, and found my speaker shirt from the Visio Solutions Conference in 1997. This was the first time that I spoke about my use of Visio in the workplace. Back then I was automatically creating dealer desk layouts from a Sybase database for a major bank in London. Next week, I will be at MS Ignite in Orlando, demonstrating how Visio and PowerBI can provide a searchable, updatable dashboard of a data center. If you are there, then I would be delighted to meet you.
Temporary Fix for Data Refresh in Visio Click-2-Run
Visio is an enormous application with literally millions of lines of code, so it is inevitable that bugs creep in for time to time, and can lay dormant .. until you really need it! Such an incident happened to me during a project for a large organisation where the latest and greatest build and versions are held up by the internal IT departments until they are sure that there is absolutely nothing hidden inside. In this project, I was given a laptop with Visio Pro for Office 365 to work with … not a problem, even though that moniker already told me that this was a seriously out of date edition, since it has been called Visio Online Plan 2 for quite a while. Anyway, I developed a solution that relies heavily on linked SharePoint lists and document libraries, using a view. The automatic name of these views are very verbose, so I consistently renamed them. Also, I had the same SharePoint Document library view linked more than once, so that I could link multiple rows to shapes, so renaming was, and is, absolutely essential. Several weeks went by, and my solution was working fine, until one day last week, my colleague told me that the Data / Refresh All was failing for him, and for other users. A review of his laptop showed that his Visio version had been updated to build 1708 from 1609 and the refresh was reverting the carefully renamed data recordsets back to the underlying SharePoint view name. My own personal laptop, not the client’s, is at build number 1808, so I will get the real fix from Microsoft soon via the normal channel updates for Click-to-Run.
