“Using the Visio ms-visio:nft function does not set the Save As location.

For example, when using...

ms-visio:nft|u|https://[path]/Test.vstx|s|https://[path]

This should create a new Visio drawing based on the template given, and set the default save location to that specified with the 's' command.

What happens though is the Visio file is created, but the default save location is NOT set which is a major problem for our integration.

This doesn't work for any Visio template. We can reproduce on any version of Visio and with local and http file locations.

There is no error reported.

Note: the same function DOES work for MS Word: ms-word:nft|u|https://[path]/Test.dotx|s|https://[path]”

Using fields in MS Visio is great opportunity!!!
Users often needs use many fields in global document-level.
For example in MS Word application in Advanced properties window of document, you can find tab named Custom. In this tab users can add so many customer properties as they need. Users can use values of these custom properties in fields in document content.
Now we can use ShapeSheet cells in Document level (a.k.a TheDoc), but it is way for advanced users. If developers add this opportunity it makes using fields in MS Visio documents more user-friendly!
---------------------------------------
Использование полей в MS Visio — отличная возможность!!!
Пользователям часто требуется использовать большое количество полей на уровне документа.
Например, в приложении MS Word в окне Расширенные свойства документа, вы можете найти вкладку с именем Custom. На этой вкладке пользователи могут добавлять столько пользовательских свойств, сколько им нужно. Пользователи могут использовать значения этих пользовательских свойств в полях в содержимом документа.
Сейчас мы можем использовать ячейки таблицы свойств ShapeSheet уровня документа (TheDoc), но это способ для опытных пользователей. Если разработчики добавляют эту возможность, то это делает использование полей в документах MS Visio более удобным для пользователей!

For multi-monitor setups allowing child windows to be separated from the single host app window would be extremely useful, as per Excel: https://blogs.office.com/en-us/2013/02/07/open-excel-workbooks-in-separate-windows-and-view-them-side-by-side/, or, ideally, using Visual Studio's tear off windows, out of the main app into some spare screen space.

Although you can stretch the app window across multiple monitors the break between two monitors never sits in the right place (ie the break between two child windows) and so you end up using a single monitor.

In Visio, it's common to have multiple ShapeSheet windows open at once, either displaying master and instance, or one for each sub-shape in a group. In my setup (28" 3840x2160 @ 125%) I recon on one drawing window + a maximum of five ShapeSheet windows as being usable, but beyond that you spend all your time scrolling and switching windows. One of the real benefits of a large screen in Visio is being able to see more ShapeSheet sections at once and this is limited by only being able to use a single monitor.

From the drawing window perspective, other scenarios might also include: a) master details view - for example a one window for a floor plan, displayed alongside other windows of the same page at different zoom levels and areas of focus, b) multi-page view - ie one window per page

Bottom line - I've got plenty of screen real-estate and I'd like Visio to make full use of it so that I can be more productive.

All of the arrow ends I've seen in Visio point "towards" the endpoint / shape. I was surprised to see that I couldn't find a simple radio button or similar to set the direction of the endpoint to point AWAY from the endpoint.

When creating a diagram with long connectors it is very useful to have an arrow at the beginning of the connector showing the flow of (data; process; etc.) AWAY from the "source" shape while the arrow at the "destination" shape points TOWARDS that shape.

I've learned to create custom endpoints but this is extremely time-consuming with the remnants of an ancient UI. Also, there doesn't seem to be any way with custom endpoints to show a short segment of line between the custom endpoint and the shape so that the custom shape doesn't seem to become part of the shape to which it is attached.

I created narrow rectangles in my custom endpoints to serve that purpose but they don't really match the width of the line itself except by coincidence.

Bottom line, the custom endpoint option is cumbersome while the concept of "away" / "towards" would be simple to understand and to use.