Visio for Developers
Welcome to the Visio for Developers feedback forum! We love hearing from customers and partners. To help us make Visio more awesome, we have partnered with UserVoice, a third-party service, to create this forum to hear your ideas and suggestions. Your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy , including the license terms. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.
- As soon as you start entering a new idea, a list of similar ideas might show up, allowing you to either vote for an existing idea or create a new one.
- There is no restriction on votes but you can vote any idea only once. hence vote for ideas that you want to see in future releases of Visio
- You can add #hashtags to your idea description for tagging! it makes it easier to search for similar ideas.
Looking forward for your ideas
-
I suggest you generate diagrams from Azure Resource Manager (ARM) templates similar to ArmViz.io
Allow the generation of Vision Diagrams from ARM Templates. Ideally this would be via the command line so that this could be automated as part of the continuous delivery pipeline. Other tools like http://armviz.io allow the visualization of templates, but don't allow the saving or exporting of the diagram. The Developer Tools team is also looking at a similar solution. You guys/gals should talk. This would allow solution engineers and architects to generate diagrams from templates, reducing the burden to create Minimum Viable Documentation.
29 votes -
Local storage for macros, which available for all documents
MS Excel Application have personal macro workbook (Personal.xlsb), MS Word Application have personal template with macros (Normal.dotm). Macros which contained in these storages can be called from any word's document or excel's workbook. But in Visio application there is no place where you can store macros available at the application level !
IMHO: If Visio Team add a similar feature it will be great !
17 votes -
Better Integration with Visual Studio
Other than VBA, there is no easy way to create a Visio Solution in Visual Studio. One of the stumbling blocks is including Visio templates in the solution.
13 votes -
IsSelected and IsMouseOver ShapeSheet cell
Add IsSelected and IsMouseOver cells to enable geometry and formatting changes to be applied while the shape is in a selected state (or mouseover).
Dynamically show and hide shape and sub-shapes elements based on the two states.
12 votes -
Transfer User Defined Cells on Shape Replace
When using the Shape Replace feature, the User Defined Cells are not transferred to the new shape.
11 votes -
For Visio for the Web, make the Visio JavaScript API also available when Visio files are stored in a third party database.
For Visio for the Web, make the Visio JavaScript API also available when Visio files are stored in a third party database.
At the moment we can use the Visio JavaScript API to interact with shapes of the diagram presented in Visio for the web. (https://docs.microsoft.com/en-us/office/dev/add-ins/reference/overview/visio-javascript-reference-overview)
But for this to work the Visio files needs to be stored in SharePoint or OneDrive.When you have implemented the WOPI protocol you are able to view documents using Visio online that are stored in a third party database (https://wopi.readthedocs.io/en/latest/).
We are in need of the Visio JavaScript API…10 votes -
Complete the CoAuth API
Give us a chance to follow up changes while merging two versions. 3rd party tools need to catch up. Currently the API does not even give a hint what has been changed.
We actually disable CoAuth in our solution since it makes our documents inconsistent.9 votes -
Reverse and Forward Database Model using Visio
I remember Microsoft Visio for Enterprise Architect, and how i can modelate a sql database using Visio.
I don't understand why you remove this feature, today it's only able to reverse engineer a database using Visio Pro for Office 265, but it's not possible forward to database.
I know a lot of people with the same problem, i'm still using Visio 2003 for Enterprise Architects today (now in 2017), and i will be happy if you give us this feature back!
8 votes -
Quick Shape API
Give us programmatic control which quick shapes are being displayed. We need to manipulate which shapes may be connected to other shapes in a specific context. E.g. in EPC you may never connect an Event with another Event. This functionality is provided by many process modelling tools.
Quick Shape information is currently stored in an encoded string in the registry
8 votes -
Shapesheet function for connection point connected
It would be helpful to provide a function via the shapesheet for connections to be able to determine if they have a connection or not.
7 votes -
Provide a Visio Rest Api with support in MS Graph
MS stated future for extending Office applications in via a Rest Api and support for MS Graph.
Imagine asking a Skype Bot to draw a diagram of network devices that can be discovered, or create an orghart of someone's team, or create a flowchart of steps required to achieve a goal...7 votes -
Enable creation of diagrams not tied to physical page constraints.
I produce diagrams never intended to be printed out - network diagrams, database schema, et al. It is extremely constraining to have to be juggling shapes around to fit in some arbitrary A4 / A3 / whatever sized paper background and always see those edges locking in my work. Let me just have an infinite blank canvas. Or if that exists in Visio, I cannot find it.
7 votes -
Open API of Org chart.
I want to create custom Org chart wizard.
Because Standard function cannot suport Japanese rule.7 votes -
Open up ShapeSheet window API access
To allow tool makers to access things like scroll position (scroll a given cell to view), cell background color, cell tooltips, context menus etc.
6 votes -
Expose more of the visio object model to VBA, and provide full VBA help documentation
In a prior role, I used VBA to automate Visio- things like adjusting the shapes, overlaying external color-coded shapes on org charts to illustrate aspects of the work, etc. In more recent versions of Visio, I think there is a lot more going on (maybe to make it more functional for a variety of other user needs), but it has become more difficult (at least for me) to understand the object model, and often I have to go to other experts because tribal knowledge has replaced comprehensive documentation.
Perhaps embedded in this suggestion is a review of the nomenclature for…
5 votes -
Allow use of VBA macros to 'polish' Data Visualizer drawings including: activate Data Graphics, select DG fields, and configure DG.
Currently, the Data Graphics window closes and becomes disabled as soon as you start recording a macro..so you cannot create VBA code to automate standard DG configurations that may be needed. This is very annoying when you have tens of drawings to produce with identical configurations and you are trying to make it easy for Visio beginners to perform on a regular basis.
4 votes -
A shapesheet function to parse a string from a shapesheet cell's formula.
The purpose I'm thinking for this, is to make possible to get strings of Name or NameU properties automatically with a dynamic connector, making possible to get and send data between shapes by connecting them with a dynamic connector, using only shapesheet functions.
4 votes -
4 votes
-
Make connection points visible when a glueable control point is dragged near (as for connectors)
The idea of hiding connection points and only showing them when the end of a connector is dragged near to a shape works fine. However, this does not work for control points that can be glued, seems to be an oversight. The connection points should be shown when the control point is moved near to the shaoe.
4 votes -
Automatically strip preceding 'User.' and 'Prop.' when pasting cellnames into respective section
If you're copying Shape Data or User cell names across from one ShapeSheet to another, automatically strip any preceding 'User.' or 'Prop.' from the name so that an error is not generated and allows the user to paste in a single operation.
Currently you have to copy the source cell, select the target cell, dbl click or F2 to enter edit mode, paste the name including the prefix, move the cursor to the right place and then delete the offending characters and finally hit enter to commit the change.
4 votes
- Don't see your idea?