One implication I have run into with multiple exernal id types is in extracting (for example) a receiver id from an internal document submitted to TN for recognition.
On the Extract tab for the document type, you can key in an xml query string to grab the id, but you select the external id type (the “transformation”) from a dropdown list.
I have never understood why a TN doctype grabs the external id type for the sender/receiver attributes this way. I’d much prefer to be able to enter an xml query string to extract the external id type just like the id itself. In this way, the same TN doctype would serve for all possible external id types.
Since I don’t want to multiply my internal TN doctypes by the number of external ids I support, the implication of this for me has been using the required id type (usually DUNS) for all “internal” receiver id purposes, and then using some other process to set the “external” ids (usually when I am building X12 envelopes) before sending to a trading partner.
Do you use a different mechanism for getting the external id type in your TN document type definitions so that TN can recognize the receiver when the document is submitted with multiple external id types?