Sage 100

I'm working on a VI job to import AP invoices. All is going well. However, we have one UDF column (field) that contains a well name. The UDF is 1,024 characters so they can enter an entire well name and description. This includes Line Feeds. When I try to import this data instead of entering it through the interface, the line feeds cause the import to fail. Any idea on how to get VI to import the data with the line feeds or am I out of luck?

Just a thought. Try tab delimiting the source file.

No, the more I think about it, it's going to see the CR LF as the end of the record.

I don't know that I have any options. will either have to strip the line feeds, break the data into components and then try to reassemble in VI, or just punt and bring in the first line or all lines separated by Pipes or something. Time for the client to make a decision and move on! Cheers.

What is the data type of the source file? If you can get it to Excel, you could scrub he data by performing a find and replace Find 010 and replace with blank (hit the space bar or just leave the replace field blank). Also find 013 and replace with blank.

I figured I could strip out the line feeds. I wanted to leave them and import the text with them.

What does Sage use for a line feed/carriage return when you type a comment by hand? Perhaps it would import if your replaced the 010 and 013 characters with what Sage uses. Many years ago, I think we had to escape certain characters to keep them from being acted on.

@ShawnSlavin I don't know if this would work in your case, but check out the solution @EricAnderson posted on this thread: https://90minds-com.socialcast.com/messages/7108278 You'd have to replace the CRLF with another character before importing but I think the logic would work.

That's the most likely idea to work I've seen yet. not sure how providex's substitute command works but you might need to replace both characters. ie CR(chr(13) with | and LF(chr(10) with ^ then put them back with the substitute in the VI job.

I haven't tried Robert's suggestion yet but I will shortly. Brett, looking at the data that we pulled through a pass-through query, there is a line feed (Chr(10)) but no carriage return (Chr(13)). We replaced the line feed with space | space in the import file so I have something to match.

I found this when searching for an answer for another import problem. Add ~;~ to the source file to add carriage returns.