This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
However, when I run these through the 'Input Data' tool it seems to ignore the 'translate' tag and attributes, and the result is the same as running without it, defaulting to using the 'Code Page' translation that is selected by defaut. Is there something I'm missing to set up the tool to read using the XML?
It has been years since I worked with mainframe data via Alteryx. While you're waiting for a suitable response here, please open a ticket email@example.com to see if someone there has a ready solution. I might have time to work with you later this afternoon (Eastern) to try to work this out. If you PM me with your address, I'll let you know my availability should you not get an answer.
Alteryx ACE & Top Community Contributor
Chaos reigns within. Repent, reflect and reboot. Order shall return. Please Subscribe to my youTube channel.
@EricWe thank you! That was my problem (at least one of them) ... I was importing the .flat file into the workflow and embedding the field setting in the Workflow. Changing to the option use the field settings from a file got results!
My other issue was I still had a couple attributes that weren't capitalized correctly, but the first one was the major one. Here's my final XML for those that are curious: