Transfer UN Data can incorrect set the terminal ID when the Utility Network has more than one terminal with the same name

Hi everyone,

We are honestly not sure if this is a bug or a user error, but we have poured over this AP and our Network Rules for quite some time now without any results. If this is not the right place for this post, please let me know.

Using the Transfer Utility Network Data tool: when trying to import an AP containing two features and a junction-junction connectivity association between the two, the following error gets thrown:

These features and their C_Assoc row are created using an FME process. These are the rows:
Electric Junction:

Electric Device:

C_Associations:

This is the rule in our Utility Network:

This is the rule in the B_Rules table:

This is the Eathing Transfomer Terminals row from the Terminal Configurations of our Utility Network:

These are the settings of our Electric Network for resp. Electric Device and the Electric Junction:

The AP is created using FME. Other AP's from the very same FME Workspace are imported without any issues. This is also why I am sure that the features and their assoc are not already on the service. All other features and associations in the AP were imported without any issues, but its this one that throws an error.

Things we have tried:
- Checked all columns of the assoc row for trailing whitespaces.
- Editing the asset types in the assoc row so all three languages are present.
- Creating the same assets + the assoc in a branch on the service, this goes without issues, also: the accompanying row in the UN assoc table looks very similar to the AP's C_Assoc table.
- Exporting the data from above to AP, then importing again in a different branch. This threw the same error. (this is what my comments on the other issue were about)
- Creating the same assets on the service _without the assoc_ in a branch, importing an AP with only the association row to the same branch. This threw the same error.
- Importing other features with junction junction connectivity assocs with the same Electric Device asset type (but a different terminal), these assocs were imported without any issues:

Again: this could very well be a user error, but we are kind of lost in what else we could check. Do you have any tips for other things to try? Also, please let me know if you need any more details from us.

AGP 3.5.4
UDMS 3.5.0.1

Kind regards,
Joep