This topic contains 4 replies, has 0 voices, and was last updated by rsm_ryan_meyer 7 years, 11 months ago.

  • Author
    Posts
  • #5081 Score: 0

    rsm_ryan_meyer
    • Contributions: 0
    • Level 1

    Is there a formula to remove carriage returns from fields in a Saved Search? I have a custom Text Area field that is being used by a 3PL integration and have discovered that if the user hits enter within that Text Area field, the 3PL’s system sees that as a new line when it shouldn’t. I’m hoping to “scrub” the carriage returns out via formula before the data is sent to the 3PL.

    I tried the REPLACE function with
    , ‘
    ‘, /n and ‘/n’ based on some info I found on SuiteAnswers. No luck. Thanks!
    This is a cached copy. Click here to see the original post.

  • #5082 Score: 0

    ERPExperts
    • Contributions: 0
    • Level 1

    Just to check, have you tried n as that’s the correct way around?

  • #5083 Score: 0

    rsm_ryan_meyer
    • Contributions: 0
    • Level 1

    Thanks for the reply.

    I figured out what works for carriage return (chr(13) is apparently the code representation of CR); this formula is apparently finding the CRs:

    REPLACE({custbody_field},chr(13),”)

    However, when I export to Excel, they are still there. I know the formula is finding them as I modified it to REPLACE({custbody_field},chr(13),’aaa’) at one point and the ‘aaa’ was showing up in the correct places in the results. I tried REPLACE({custbody_field},chr(13),’ ‘) , REPLACE({custbody_field},chr(13),”) , REPLACE({custbody_field},chr(13),null) and REPLACE({custbody_field},chr(13)).

    Results of all those test still send CRs to Excel. It’s like the NS results are overriding the formula. Any other thoughts?

  • #5084 Score: 0

    dominicb
    • Contributions: 0
    • Level 1

    Have you tried replacing chr(13) and chr(10) in case its an LF rather than a CR?

  • #5085 Score: 0

    rsm_ryan_meyer
    • Contributions: 0
    • Level 1

    Thanks for the reply. I did end up using that and replace(replace(Name,CHR(10),”),CHR(13),”) ended up working for me.

You must be logged in to reply to this topic.