Re: Flat File Problem

Rather than modifying the flat file why don't you promote the property
yourself in your custom pipeline component.
baseMessage.Context.Promote("RecordCount", "Your RecordCount property
namespace", record count value);
You can do this just before returning from GetNext()

This would be much easier than modifying the input data, using a header
schema and relying on the FFDasm to promote the property for you.

The FFDasm will promotes properties
And you can promote properties from the Header into the message context, and
have access to them in the orchestration. If the input message is split by
the FFDasm each message will contain the header properties.

Greg


"Leonid Ganeline" <leo_gan_57@xxxxxxxxxxx> wrote in message
news:%23$B2qd6RGHA.256@xxxxxxxxxxxxxxxxxxxxxxx
Hi Gary,
As I can remember the header information is not accessible inside the
Orch. It is only immutable transfering from receive port to the send port.
Why do you use a header schema?
If you anyway use a custom pipeline you can add a node with a record ID to
the body schema.
Keep in mind that XmlDisassembler component promotes nodes to the context.
No XmlDisassembler - no promotion.

--

Regards,

Leonid Ganeline
BizTalk developer
Vancouver
http://geekswithblogs.net/leonidganeline
===================================


"Gary" <Gary@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B924A764-3FAC-48D7-813C-AC182E8A4D9D@xxxxxxxxxxxxxxxx
Hi All,

I am currently working on a project where we receive a flat file which
contains no header or trailer but multiple records in the file. We are
wrapping the FFDasm in a custom pipeline so we can dynamically set the
schema
property.

What we are wanting to do is use a sequential convoy to enforce
sequencing.
Therefore we have figured that we could do this by counting the records
in
the flat file and then updating the stream by inserting our own header
record
before calling the FFDasm disassemble method.

We have currently hard coded the head so our file is as follows:

RecordCount2
Rec....... etc
Rec....... ect

We have assigned a schema to the DocumentSpecName and also a header
schema
to the HeaderSpecName. Our problem is we dont know how to get the value
from
the Header in an orchestration. We have tried promoting the RecordCount
property in the header schema and setting the promoted element to
MessagePropertyContextBase and we have set the PreserveHeader property to
true in the pipeline component but it doesn't seem to be populated in the
orchestration.

Can anyone give us a clue with this one please?

Cheers,
Gary




.

Relevant Pages

  • RE: Flat file ASSEMBLER example
    ... I've created flat file schemas with header, body, and footer records. ... Add a New Item and select schema. ...
    (microsoft.public.biztalk.general)
  • Re: Flat file XSDs
    ... Root delimiter PostFix Hex "0x0D 0x0A" ... I have created a schema that will parse your sample data. ... line into the header. ... wholely unsuited to import by BizTalk Flat File Schema Wizard. ...
    (microsoft.public.biztalk.general)
  • RE: Global variable %SourceFileName% to Map?
    ... not sure how I would get the property into the schema in the first place. ... to get that property included in my inbound schema for custom pipeline I ... > I think you cannot access the context properties in a Map ... I have a flat file custom ...
    (microsoft.public.biztalk.general)
  • Re: Flat File assembler with header
    ... >> header and body have not same number of field. ... >> how can i use the custom send pipeline with a flat file assembler to ... > is that the header schema has a set of promoted properties. ... Yoann ...
    (microsoft.public.biztalk.general)
  • Re: Header Question - round 2... nobody responded
    ... I thought the flat file assembler would deal with headers as well (but I ... Is it possible that you want to have a multipart message (with both header ... body schema that the right thing will hapen? ... >> schema (for the output document). ...
    (microsoft.public.biztalk.general)
Loading