You are absolutely correct. tn:receive does this as a security check. Take a look at the eZine article by Sonam Chauhan. [url=“wmusers.com”]wmusers.com
It describes the situation and a solution.
Mutually Defined is a good ID to use as the required ID type. You should probably avoid using a custom ID type as the required ID type.
Multiple DUNS (or any type of identifier) is indeed an issue that TN doesn’t address very well out of the box. You can either assign the use of the User Defined X IDs or add your own.
The main issue for EDI is that the mapping of qualifiers to ID types is grossly limited. As you stated: 01 = DUNS, ZZ= Mutually Defined and all other qualifiers are assumed to be User Defined 1 external IDs. What’s needed is the ability to associate multiple identifiers of a given type with a single profile, including the “My Enterprise” profile.
The project I’m working on is trying to address this right now. I’ll post what I can. If you come up with something please share if you can.