Data Mapping with Transaction Matching
SummaryIssue with more than 20 source columns
My client has 25 columns they want to bring in for reference in transaction matching. When I create the local TM source, the additional columns are defined as attributes by default. The attribute columns do not show up in the mapping, and when I map the UD columns, the load fails in the transform stage. When I delete the attribute fields from the target application, it succeeds. Any ideas on how I bring in the additional 5 columns?
I was unable to find any documentation on how to configure this.