Forum Replies Created
-
Posts
-
Thank you for your help.
when I dont have optional filed Why is it create xml above that field level and skipping the rest?
for example.. if I dont have H02 ( which is optional) in my flat file, then xml created about HO2. So I am losing D01, D02 which are under the H02 in the schema and flat file.
"
Server Error in '/' Application.
The resource cannot be found.
Description: HTTP
404. The resource you are looking for (or one of its dependencies)
could have been removed, had its name changed, or is temporarily
unavailable. Please review the following URL and make sure that it is
spelled correctly.Requested Url: /BTARNApp/RNIFSend.aspx"
I think Stephen is maybe talking about Ignore CR and Ignore LF? That is for handling parsing issues of the DOS pair CR/LF (hex 0D/0A), which is two chars instead of just one.
If I understand correctly it sounds like there are two CR/LF at the end of your flat file? Try creating an outer record around your file that can absorb the extra CRLF.
Otherwise explain the issue again if I have not understood it. I just made some FF schemas recently, so I have the info fresh in my mind.
– weak architect
You made it too complicated. Here:
Function Lookup (parameter_in)
Select case parameter_in
case "Y"Lookup = "Approved"
case "N"
Lookup = "Denied"
case "U"
Lookup = "Unknown"
case else
Lookup = ""
End Select
End Function
This might use less object invocation.
– Weak Architect
BizTalk 2006 R2 will do this no problem – just wait until September 2007 when it is released. Maybe it will even be a free upgrade.
If you simply must have the functionality now, there is an article about hacking the Base EDI adapter to work with your own schema. Stephen has the link or you can page back in the forum to find it.
To parse the whole file into one message with multiple documents you need a schema like this, the child order is critical:
root (hex 0x0D 0x0A postfix)
–document (hex 0x0D 0x0A infix maxOccurs=*)
—-header (positional tag=Header01)
——fields
—-details ((hex 0x0D 0x0A infix)
——detail (positional tag=Detail01 maxOccurs=*)
——–fieldsTo debatch into separate document messages in the pipeline, change the maxOccurs of the document node to 1
thank you,
I fixed it, Now i have another issue:
The error is:
Unexpected DataFound while looking for:
'D01'
'\r\n'
'S01'
The current definition being parsed is POInfo. The stream offset where the
error occured is 3675. the number where the error occured is 16. the column
where the error occured is 0.The D01 is repeating record. The next record type is S01. I have 4 D01
lines. The next line is S01. why is it still looking for D01?
The D01's Max Occured set as "Unbounded". I can have it as much as I have.
How can i make schema to stop looking for D01 and go to next S01 element?
I am new to XML Schema, Please help me to fix this issue.You’d need to build the string as your want it inside the Orchestration. And then set that to the message body.
The properties you’d want to look at are File.ReceivedFileName (or http://FTP.ReceivedFileName , etc)or BTS.InboudTransportLocation. You might need to combine this together to get what you want.
Hope this helps.
It’s been a while but I think there is a setting to ignore trailing delimiters. I think it’s at the <Schema> level. It’s a property.
Never tried it before but it sound like it would work in your case.
It could be moving the database. But I would think you’d have other issues before this – i.e. when starting the service or receiving the file. Sorry, don’t know what else to say on this one.
Have you looked at my sample on Splitting Pop3 Attachments?
It should allow you to then same off the WinZip Attachment as is.
The sample is under BizTalk 2006 – Samples.
I don’t think that works. I don’t think items inside the message body can be promoted and demoted. If I remember right, I promote items from the Envelope itself.
I might have it back words.
In any case, I don’t think this is something you can do without custom code.
I think the easiest way would be to debatch the file into 3 separate files. I really have 3 files in one. You can do this using an envelope but probably would require a 2nd pass through BizTalk. You could also use an Orchestration to break up the message once you have it in XML.
You could probably also change your schema to support multiple files by adding a higher level root record. But in this case you’d need to redo your maps.
