VictorDV

Hi guys... it's very strange, I'm parsing an ORDERS file, using the EDIReceiver pipe, and I get:

Error: 1 (Field level error)

SegmentID: FTX

Position in TS: 5

Data Element ID: C10801

Position in Segment: 5

Position in Field: 1

Data Value: HSNC096QMA0 AMBBSEE 1 220-240V 50HZ EXPORT MODEL SCOTH & ENG

21: Invalid character found

The complete line is:

FTX+AAA+++HSNC096QMA0 AMBBSEE 1 220-240V 50HZ EXPORT MODEL SCOTH & ENG+EN'

So it's very obvious , if I remove the " & ", it works perfectly.

What would be the solution in order to biztalk process the file correctly without the replace and including the & char I double checked the characterencoding of the pipeline and it's UTF8 . It's a very basic thing. I get it also with others , for instance : ****** .

Any help would be greatly appreciated.

Victor



Re: BizTalk EDI and AS2 EDIFACT Ampersand and other characters problem..

Richard

Hi Victor,

Which syntax are you using - UNOA If so, the "&" is an invalid character. I understand this can't currently be configured but maybe someone else on the forum can calrify that.

Richard





Re: BizTalk EDI and AS2 EDIFACT Ampersand and other characters problem..

VictorDV

Thanks for the answer Richard. Indeed it's UMA, as the heading indicates, here:

UNB+UNOA:3+

It's strange that I got a message with a forbidden character, if that's the case how could they generate the orders file then.





Re: BizTalk EDI and AS2 EDIFACT Ampersand and other characters problem..

Richard

As it is very common that users do not follow the character set restrictions, many EDI products allow this check to be configured / relaxed.





Re: BizTalk EDI and AS2 EDIFACT Ampersand and other characters problem..

Leonid Ganeline - MVP

Richard575902 wrote:
As it is very common that users do not follow the character set restrictions, many EDI products allow this check to be configured / relaxed.

Absolutely!
We also discussed this problem on this forum.
MSFT knows about this and maybe in the next release there should be symboldecoder pipeline component or something else.
Now we have to use preprocessors.





Re: BizTalk EDI and AS2 EDIFACT Ampersand and other characters problem..

VictorDV

Thanks Leonid , anyway if it's a limitation of the UNOA as I checked on th web is also a mistake from my trading partner to generate a file with forbidden characters.





Re: BizTalk EDI and AS2 EDIFACT Ampersand and other characters problem..

Genuine Basil

even i am also facing this same problem and planning to have a preprocessor to remove &. could u please let me know which are the otherforbidden characters in UNOA so that we coudl take precaution.. it would be great if you share (link) more information on the standards..

thanks.. Smile




Re: BizTalk EDI and AS2 EDIFACT Ampersand and other characters problem..

Richard

Unlike X12, all EDIFACT details can be obtained from their web site http://www.unece.org/trade/untdid/welcome.htm





Re: BizTalk EDI and AS2 EDIFACT Ampersand and other characters problem..

Genuine Basil

I used EDI Data Validation property in pipelines to false.. since i just need to split interchanges and route it..






Re: BizTalk EDI and AS2 EDIFACT Ampersand and other characters problem..

jftl6y_007

Basil,

My specific problem is mapping an address field with a "#" character (e.g. 123 Anystreet #10) to various fields in a D96A_PAYMUL file and am getting the invalid character errors. When you say you set the EDI Data Validation property in the pipeline to "false" do you mean the defaul EdiSend pipeline Or did you create a custom pipeline Even though this appears to be invalid syntax, my customer says "This is the way it's always been so make it work."

Cheers.





Re: BizTalk EDI and AS2 EDIFACT Ampersand and other characters problem..

Genuine Basil

In my case, i was receiving a file with '&' in one of the fileds.. so in EDI Receive pipeline I set data validation to false and I was able to receive and sent EDIFACT interchange without any error (setting data validation false in EDI Receive and Send Pipeline)...

I am using a D96ASurpriseRDERS (UNOA) format and I tried adding '#' to 'C05904' field ( i guess this is part of the address) and I was able to receive and sent message setting data validation false in standard EDI Receive and Send Pipeline..

hope same way u could solve ur issue..