We are directly updating .vsdx XML files to update shape data and then using Aspose.Diagram to convert the .vsdx to .svg.
Presently, we use a NewValue processing instruction (https://msdn.microsoft.com/en-us/library/office/jj649391.aspx#sectionToggle5) to ensure Visio picks up the change and displays the new value for the data.
The Shape class offers refreshData() method which you can call before exporting VSDX drawing to SVG format. Kindly send us your VSDX drawings with and without XML updates. We will investigate and share our findings with you.
Attached is an example showing a rectangle with a shape data field of “CogniDox_Partnum” set. In the original version this is “TOBECHANGED”, in the modified version, it’s “AA-000830-AW”. In the XML, we’ve updated the property value in shape ID 2, and the text call-out ValueText in shape ID 3, putting in the NewValue processing instruction. Opening the modified file in Visio updates the value in the call-out. However, saving as SVG with Diagram keeps the “TOBECHANGED” text.
Iterating through all the shapes and calling refreshData on all the shapes throws exceptions for shapes 1 and 2, and is OK for shapes 3 and 4. However, it has no effect on the SVG output.
We have logged an enhancement ticket ID DIAGRAMJAVA-50592 in our issue tracking system. We have linked your post to this ticket and will keep you informed regarding any available updates.
The issues you have found earlier (filed as DIAGRAMJAVA-50592) have been fixed in Aspose.Diagram for Java 18.3 API. This message was posted using BugNotificationTool from Downloads module by imran.rafique
The issues you have found earlier (filed as ) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by MuzammilKhan