WPF Diagram Problem with serializing the generated xaml file

I have enabled automatic port generation, and after the connector is connected to the automatically generated port, there is no relevant target id and target port id in the connector part in the serialized generated xaml file. The performance is 

<TargetId i:nil="true" />

< TargetPortId i:nil="true" />.

But if I connect to the manually created port instead of the automatically created port, the target id and target port id exist in the connector section of the serialized generated xaml file as 

<TargetId i:type="a:guid" xmlns:a= "http://schemas.microsoft.com/2003/10/Serialization/">e2456eed-6265-4bb8-a2f0-cfc31ddb8db1</TargetId>

<TargetPortId i:type="a:guid" xmlns:a="http://schemas.microsoft.com/2003/10/Serialization/">5183f7b1-2e3e-4f4f-8e11-457b24ac5b6a</TargetPortId>


8 Replies

DT Deepa Thiruppathy Syncfusion Team March 2, 2022 10:44 AM UTC

Hi NIma, 
 
Reported issue: Serialized file is having Target ID and Target Port ID as null when connector drawn using AutomaticPortCreation.  
 
We have validated this issue in a simple sample by drawing a connector from one node to another node through AutomaticPortCreation process at run time. IDs of TargetNode, SourceNode, SourcePort, TargetPort objects are serialized properly.  
 
We have attached the sample that we have tried. Please make changes to that sample to reproduce this issue or provide any video representation to know how you are created a connector and automatic ports. Also please confirm the product version that you are using. So that we can assist you further. 
 
 
Regards, 
Deepa Thiruppathy 



NI NIma replied to Deepa Thiruppathy March 2, 2022 07:05 PM UTC

Thanks for your reply, I downloaded the example you posted. In the example, a connector connecting node and node has both target id and source id, but if a connector is not connected to two nodes, but one node and one in another For a port automatically created on a connector, the target id cannot display the id of the port automatically created on another connector



DT Deepa Thiruppathy Syncfusion Team March 3, 2022 10:05 AM UTC

We are able to reproduce the issue. We have logged the bug report and the fix will be included in our upcoming weekly NuGet release which is expected to be released on March 8, 2022. 
  



DT Deepa Thiruppathy Syncfusion Team March 8, 2022 02:54 PM UTC

  
Sorry Tealer. We have fixed the reported issue but could not be able to include the fix in our weekly NuGet package. 
 
Please find the patch details as below,  
 
 
Recommended approach - exe will perform automatic configuration 
 
 
Please find the patch setup from below location: 
 
 
  
Advanced approach – use only if you have specific needs and can directly replace existing assemblies for your build environment  
 
Please find the patch assemblies alone from below location:   
 
  
NuGet Link:  
 
 
 
Assembly Version: 19.4.0.48 
 
 
Installation Directions:   
 
This patch should replace the files “Syncfusion.SfDiagram.WPF.dll” under the following folder.  
 
$system drive:\ Files\Syncfusion\Essential Studio\$Version # \precompiledassemblies\$Version#\4.6  
 
Eg : $system drive:\Program Files\Syncfusion\Essential Studio\19.4.0.48\precompiledassemblies\19.4.0.48\4.6 
 
 
To automatically run the Assembly Manager, please check the Run assembly manager checkbox option while installing the patch. If this option is unchecked, the patch will replace the assemblies in precompiled assemblies’ folder only. Then, you will have to manually copy and paste them to the preferred location, or you will have to run the Syncfusion Assembly Manager application (available from the Syncfusion Dashboard, installed as a shortcut in the Application menu) to re-install assemblies.  
 
  
Disclaimer: 
 
Please note that we have created this patch for version 19.4.0.48 specifically to resolve the issue reported in this forum 173310.  
 
 
If you have received other patches for the same version for other products, please apply all patches in the order received. 



TE tealer replied to Deepa Thiruppathy March 8, 2022 06:48 PM UTC

I have updated the nuget package released on March 8th, but the problem remains, the connector still does not have a target id when connecting to an automatically created port on another connector.



NI NIma replied to Deepa Thiruppathy March 11, 2022 07:02 AM UTC

Thank you Deepa and Syncfusion group, I have installed the patch in the link and it works fine.I would like to know when the fix for the issue will be included in the offical release so that I can uodate to the latest diagram package.



DT Deepa Thiruppathy Syncfusion Team March 11, 2022 11:41 AM UTC

Fix will be included in our upcoming weekly NuGet release which is expected to be released on March 15, 2022. 



DT Deepa Thiruppathy Syncfusion Team March 16, 2022 06:34 AM UTC

Reported issue: Serialized file is having Target ID and Target Port ID as null when connector drawn using AutomaticPortCreation. 

We are glad to announce that our weekly NuGet was rolled out and fix for the reported issue was included in the weekly NuGet.  

NuGet Version: 19.4.0.56 



Loader.
Up arrow icon