Software Engineer Integration Specialist Frontend Developer Solution Architect
Hey Paul,
Half agree if the OP requirements turn out to be a file to file use case.
If not, I wanted to defend the record mapper solution a little so as not to put off other readers from this approach.
As an example, I recently implemented a solution that had a million line CSV file. This would generate around 300,000 messages from a complex mapping. Each record was individually passed into a DTL which in turn produced a master file update message. These were then pushed into the local EPR (as per the EPR's requirements).
Yes, many messages, but not what I would call an overhead when taken into context of the frequency and need for M16 messages.
Bottom line, the solution I selected was the most maintainable solution. Almost zero glue code to go wrong and all maintanence managed inside DTL's. This is exactly what the record mapper was designed for.
Hi Thom,
What are you trying to do with the data?
Rereading your original post, you say you want to make a slight transformation to the file, which almost suggests the end result is another CSV file?
Perhaps if you could expand the requirements a little then it will be easier to point you in the simplist direction.
Hi Scott,
Probably best to avoid modifying the Ens.MessageHeader properties, doing so might affect trace logging and potentially lead to unexpected side effects.
Here are a few alternative ideas....