FlatFile Disassembler eats almost Everything (and that’s not what i want)….

Home Page Forums BizTalk 2004 – BizTalk 2010 FlatFile Disassembler eats almost Everything (and that’s not what i want)….

Viewing 1 reply thread
  • Author
    Posts
    • #21868

      Ok I have a very basic CSV definition, below is a sample of this….

      
      

      
      

      07;6834;IX351B;A;20090213;996;36;599813;M;K;252,00
      07;35712;IX351C;A;20090213;996;2;599813;M;K;14,00

      
      

       I ran the FlatFile Wizard and I do have a nice XML representation of this

      
      

      schema.

      
      

       

      
      

      But the problem I have is the following…….

      
      

      
      

      if I change the input file (for example add some extra fields) things start to go wrong,
      i would expect the document beeing invalid and should be
      suspended.

      
      

       

      
      

      07;6834;IX351B;Q;20090213;996;36;599813;S;U
      07;35712;IX351C;W;20090213;996;2;599813;T;V;-1114,00;QW

      
      

       

      
      

      ( First line is an item missing, second line has items too much…)

      
      

       I get this as xml….

      
      

       <FinSys-Data xmlns=”http://FH.CE.CFI.RIS.FinSys.Schemas.FinSys_FlatFile“>
      <FinSys-Data_Record>
      <Veilpunt_Verrekend>07</Veilpunt_Verrekend>
      <AdministratieNummerAanvoerder>6834</AdministratieNummerAanvoerder>
      <AanvoerBriefNummer>IX351B</AanvoerBriefNummer>
      <AanvoerBriefRegel>Q</AanvoerBriefRegel>
      <VerrekenDatum>20090213</VerrekenDatum>
      <FustCode>996</FustCode>
      <AantalEenhedenFust>36</AantalEenhedenFust>
      <AdministratienummerStatiegeldRechtHebbende>599813</AdministratienummerStatiegeldRechtHebbende>
      <FustSoort>S</FustSoort>
      <VerkoopWijze>U

       

      07</VerkoopWijze>
      <TotaalBedragFust>35712;IX351C;W;20090213;996;2;599813;T;V;-1114,00;QW</TotaalBedragFust>
      </FinSys-Data_Record>
      </FinSys-Data>

      
      

       

      
      

      This is obviously not what I want,
      Is there anybody out there who knows how to tackle this problem…..

      
      

       

    • #21888

      The disassembler has no way of knowing how big the last element (VerkoopWijze) will be – you probably have it defined as a string with no restriction.

      If you know how long that element will be (say, it will always be 1 character long), you can select the element, and in the properties change the “Derived By” to be Restriction, then change the Maximum Length property to 1, then use an xml validator component on the same pipeline as the flat file disassembler. This way you would get a message like this from the xml validator:

      The ‘VerkoopWijze’ element is invalid – The value ‘V;-1114,00;QW’ is invalid according to its datatype ‘String’ – The actual length is greater than the MaxLength value.

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.