When exporting to JSON the configurations of a RadDiagram containing complex shapes, not all of the shapes information gets exported. For example, the URLs to the embedded in the shapes images are not exported.
Posted on:18 Jan 2018 15:32
I've created a workflow solution using RadDiagram where all of the shapes are complex (see attached image). Unfortunately, all of this shape customization is lost when you perform a diagram.save because the serialization/deserialization process required to store/retrieve the diagram strips out all methods required by the visual templates used. In order to work around this issue, I'm currently having to store a "type" parameter with each custom shape and then rebuild the custom shape based on this "type" value upon diagram.load, a clumsy and time consuming process. Perhaps instead of relying solely on JSON to save/load a diagram, another proprietary mechanism could be used to get around this problem. On a related note, the ability to save/load the diagram from the server-side would also be a major plus...