# wm.b2b.edi:convertToString bad delimiter output

**URL:** <https://techcommunity.softwareag.com/t/wm-b2b-edi-converttostring-bad-delimiter-output/109279>\
**Category:** Forum\
**Tags:** EDI\
**Created:** [May 25, 2007, 8:27pm UTC](https://techcommunity.softwareag.com/t/wm-b2b-edi-converttostring-bad-delimiter-output/109279 "2007-05-25T20:27:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jim\_Plested](https://avatars.discourse-cdn.com/v4/letter/j/e480ec/32.png) [@Jim\_Plested](https://techcommunity.softwareag.com/u/Jim_Plested)\
**Post date:** [May 25, 2007, 8:27pm UTC](https://techcommunity.softwareag.com/t/wm-b2b-edi-converttostring-bad-delimiter-output/109279/1 "2007-05-25T20:27:03Z")

</div>

We are running into an issue after installing the IS 65 SP2 to our EDI cluster. WmEDI 65 SP1 is ignoring the delimiter input and using a hex00 for the segment terminator. I see there are fixes for IS6.5 SP1 that addresses this issue. Has any one seen or dealt with this on IS SP2?

---

<div class="post-metadata">

**Author:** ![reamon](https://avatars.discourse-cdn.com/v4/letter/r/b77776/32.png) [@reamon](https://techcommunity.softwareag.com/u/reamon)\
**Post date:** [May 25, 2007, 9:27pm UTC](https://techcommunity.softwareag.com/t/wm-b2b-edi-converttostring-bad-delimiter-output/109279/2 "2007-05-25T21:27:02Z")

</div>

Jim, You might check with wM tech support. As you’ve experienced, sometimes fixes for earlier versions/SPs don’t make it into later versions/SPs. There may be a separate SP2 fix or you may need to request that one be created.  
Rob

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 3:05pm UTC](https://techcommunity.softwareag.com/t/wm-b2b-edi-converttostring-bad-delimiter-output/109279/3 "2021-04-02T15:05:37Z")

</div>