Why do External IDs appear as pipe-separated values in a single row when downloading the UDA file using the “Separate row” option, and how can they be shown in separate rows?

Created by Amit Kadam, Modified on Wed, 27 Aug at 3:42 PM by Amit Kadam

The behavior of External IDs appearing as pipe-separated values (|) within a single row in UDA file downloads is intended system behavior. This is because External IDs are not UDA fields and hence are not processed through the same logic that separates UDA entries into different rows.
If you're attempting to view or analyze External IDs on separate rows, simply applying the “Separate row” option during download will not split these values automatically.
However, a workaround is available:
You can create a custom UDA field (e.g., External Id (UDA)).
Populate this new field such that each External ID appears in a separate row against the corresponding supplier.
After importing the updated UDA file, downloading it using the “Separate row” option will display each External ID as an individual row under the custom UDA column.
The screenshot below illustrates a UDA file where External IDs were added under a custom column (External Id (UDA)). Upon download, they are displayed in separate rows, enabling better filtering and analysis.