** You could create a display only field on the form you're importing to and have workflow take care of 1) the replace function 2) move to the diary field. This will prevent you from having double entries in the diary field.
--
Michiel

On 4/25/06, Aaron Keller <[EMAIL PROTECTED]> wrote:
**

We've been importing .csv files with the 4.5.2 import tool for some time.  We could modify the mapping file to include "\r\n" and that would be interpreted as char 13, and  char 10.  But since we've upgraded the server to 6.0.1, I don't really want to continue using the 4.5.2 import tool.  And the 6.0.1 import tool is interpreting "\r\n" as just char 10.  Thus the problem.

-a

 

 


From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Grooms, Frederick W
Sent: Tuesday, April 25, 2006 10:29 AM


To: [email protected]
Subject: Re: importing character 13

 

If I remember correctly I thought it only imported returns when it was importing from a .arx format.  I don't remember .csv files ever supporting return characters in the import.

 

Fred

 


From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Aaron Keller
Sent: Tuesday, April 25, 2006 9:13 AM
To: [email protected]
Subject: importing character 13

**

Has anyone noticed that the import tool changed how it interprets character 13?

 

It used to be (and this is back in the ancient 4.5.2 days) that you could include \r in your import mapping to embed character 13.  But now with the 6.0.1 Import Tool, \r seems to be ignored.  I have not tested any 5.x Import Tools.

 

Can anyone tell me another way to insert a character 13?  At this point I have to use Excel (!) to "build" a field line by line, sticking char 13 and 10 in manually.

 

 

 

Aaron Keller
ARSystem Applications Developer

 

 


 

 

 

* Email: [EMAIL PROTECTED]

 

 

 

 

 

 

 

 

 

 

__20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___

__20060125_______________________This posting was submitted with HTML in it___

Reply via email to