Disappointed to get an error when writing strings with new line characters, read from an Azure SQL origin, when written back to an Azure Synapse SQL destination.

Have specified, in the New Line Replacement Character, string of “\n” to get the data through, but the string is distorted, and potentially confused if the source string already contains whatever I choose as a replacement. So...

• has anyone found a better strategy for dealing with this issue?
• Is an enhancement planned to passed these characters through unchanged, transparently?