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>
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
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.
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.