Great thread — thanks to the Syncfusion team and community for the detailed callback workaround. Your thorough code samples and responsive support truly help bridge diagram rendering with server-callback frameworks.
Hello.
Attachment contains video and sample project. This is simple project with callback control, which really using in xaf framework. So, I need solution (if exists) with diagram control itself.
Please accept my apologies. Just wanted to minimize project and drop all dlls, but looks like it get it from another place. You could find required dlls in attachment.
Great thread — thanks to the Syncfusion team and community for the detailed callback workaround. Your thorough code samples and responsive support truly help bridge diagram rendering with server-callback frameworks.
Hi GenerativeMasters,
Thank you for the update.
Please let us know if you require any further assistance on this. We
will be happy to assist you.
Regards,
Preethi R
Thanks to the Syncfusion team and community for guiding through the callback-based rendering scenario. The workaround using JSON serialization + hidden field + client-side load seems clever and definitely helps when the standard script-initialization fails during callbacks. The sample code and step-by-step discussion make the issue and resolution process clear.
A couple of thoughts/requests for improvement:
It would be great if future versions of Diagram handle callback-based rendering out-of-the-box — so that nodes, positions, connectors aren’t lost, and there’s no need for manual serialization / load.
Also worth improving the restore logic (node coordinates/size + remove unwanted resize markers), as mentioned by other users — this would make callback integration much smoother with minimal effort.
Hi,
Thank you for your suggestions and feedback.
Please note that based on the forum history, you are currently using the EJ1 Diagram component in ASP.NET Web Forms. We would like to inform you that the EJ1 Diagram component has reached its end of support and is no longer actively maintained. While your existing applications can continue to run as-is, we will not be providing new fixes, features, or compatibility updates for EJ1 Diagram going forward, except for minimal support in rare cases of critical bugs.
For your reference, our modern EJ2 Diagram component is available, which offers:
Any suggestions regarding improvements in the EJ2 Diagram component are considered valuable and will be reviewed for possible inclusion.
Please let us know if you need any further assistance. We’ll be happy to help.
Regards,
Moulidharan