You appear to be trying to replace the carriage return + line feed at the same time, it could be that you only have a line feed or carriage return in the data.  So try replacing them separately.  This will show you what was actually stored.

SUB(SUB(CI_ExtendedDescription.ExtendedDescriptionText$, $0D$, "~CR~"), $0A$, "~LF~")

Awesome. Good thinking on the nesting. Thank you for that David. I just plugged it in and got an "Error 20 in program VIWXOY at line 0085" message. I removed the tilde symbols and tried it again. It exported everything but the data below the Extended Description column again.

SUB(SUB(CI_ExtendedDescription.ExtendedDescriptionText$, $0D$, "CR"), $0A$, "LF")

The temp field's operation should be set to Assign, not Calculated.

David - Thank you again! That did the trick. I had to change Operation to Calculate, enter the expression and then change it back to Align.

Running that expression did not seem to do the trick though. But I think that part of the challenge is solved.

I will share it just in case anyone has seen this before. My data has hidden characters - latin small s - ASCII 00DF. You can see it here. At least this is what I think it is.

I try to strip it out with an expression but it is still there. You don't see it in MS Word Pad but the main problem is that it shows up in Excel like this. It should all be on one row.

I have an open case with SAGE and they too are stumped for the time being.

Thanks for everyone's help!

Try adding a temp field with the calculation I gave above but make sure its operation is set to Assign, then remove the extended description text field.

DFDM displays non-standard characters as the Beta symbol but that isn't actually the character stored in the database.

Got it. Added a temp field then set the calculation made sure it was set to Assign but got that error again. 

Try replacing the $0D$ with the Chr function with 13 as the argument and replacing the $0A$ with the Chr function with 10 as the argument.

The forum won't let me post the actual Chr function with the parenthesis and argument.

SAGE does not like that either!

You are missing the comma separating the last two arguments.

You are missing the comma separating the last two arguments.

Also, did you type in the field name or select it from the list?

Just pulled up one of my old jobs i used for testing and noticed the table name should have a two digit number suffix before the period and field name.  Also, I see that in this test job, I did not have to use a temp field but the actual field with the Calculation operation worked.  In this example, I was only replacing the line feeds with a blank string but you can nest it to also remove the carriage returns.

That was it! Just that one comma left out on the expression. I did change to the actual field vs. the temp one and I changed from Align to Calculated. Worked and the CSV came out perfect! Thank you again!!! You are my SAGE hero! LOL

And the row in CSV: