Community

FlexiLayout multi-page problem

Hello,

I've created one flexi layout that works just fine when there is only one page.
But, as my type of file contain a table, when there is too many lines in my table, it goes on a second page. And when i try to do right-clic + Match on a double page document, flexi capture can't figure out what to do, he doesn't know witch is the first page and witch is the second one. All my fields that used work on my first page doesn't work annymore, as if my second page was considered as the first one.
It becomes really messy.

Here is what i've tried :
-Put a field in the header that is only in my first page (a static field with "Page : 1")
-put a filed in the footer that is only in my last page (static field with "Page : 2)
-Checked if my flexi layout support multi page (flexilayout -> properties minPage 1 MaxPage 2)

How can flexicapture can recognize the first page and the last page of a multi page document ?

Thank you, regards.

0

Comments

3 comments

  • Avatar
    Valembois felix

    I've forgot to send the logs. 

     

    Deleting page data... - 16:42:51 28/10/2020
    Done - 0,170 sec
    Matching the FlexiLayout... - 16:42:51 28/10/2020
    Page 1. Unmatched. Reference: <None> (page 1). - 0,066 sec
    Unable to match the FlexiLayout. - 16:42:52
    Page 2, element SearchElements.Code_CHOORUS: The search takes too long. Try optimizing the search, e.g. by restricting the search area. - 16:42:52
    The maximum number of generated hypotheses for the element SearchElements.Code_CHOORUS has been reached. Hypotheses generation for this element has been stopped. - 16:42:52
    Page 2, element SearchElements.Libellé_Livraison: The search takes too long. Try optimizing the search, e.g. by restricting the search area. - 16:42:52
    The maximum number of generated hypotheses for the element SearchElements.Libellé_Livraison has been reached. Hypotheses generation for this element has been stopped. - 16:42:52
    Page 2. Matched: SearchElements (page 1). Reference: <None> (page 2). - 5,820 sec
    Statistics: 14 blocks matched excessively.
    Done - 6,117 sec
    Average time of page processing: 2,943 sec for 2 pages.
    Matching Statistics
    Blocks.Destinataire has regions on 0 pages
    Excessively matched on 1 (pages: 2)
    Blocks.Emetteur has regions on 0 pages
    Excessively matched on 1 (pages: 2)
    Blocks.Commande has regions on 0 pages
    Excessively matched on 1 (pages: 2)
    Blocks.Date has regions on 0 pages
    Blocks.DateLivraison has regions on 0 pages
    Blocks.AdressEmeteur has regions on 0 pages
    Excessively matched on 1 (pages: 2)
    Blocks.TelEmeteur has regions on 0 pages
    Excessively matched on 1 (pages: 2)
    Blocks.FaxEmeteur has regions on 0 pages
    Excessively matched on 1 (pages: 2)
    Blocks.Service has regions on 0 pages
    Excessively matched on 1 (pages: 2)
    Blocks.Code_CHORUS has regions on 0 pages
    Excessively matched on 1 (pages: 2)
    Blocks.LibLivraison has regions on 0 pages
    Excessively matched on 1 (pages: 2)
    Blocks.AdresseLivraison has regions on 0 pages
    Excessively matched on 1 (pages: 2)
    Blocks.Code_CIP has regions on 0 pages
    Blocks.Précision_Commentaire has regions on 0 pages
    Excessively matched on 1 (pages: 2)
    Blocks.Ligne_commande has regions on 0 pages
    Excessively matched on 1 (pages: 2)
    Blocks.QteTot has regions on 0 pages
    Excessively matched on 1 (pages: 2)
    Blocks.Nbligne has regions on 0 pages
    Excessively matched on 1 (pages: 2)
    Blocks.Montant_total_TCC has regions on 0 pages

    0
  • Avatar
    ElliotG

    Using the header element of the table (column names most likely), make the nearest function closest to the Page 1 Element.  This will ensure it looks at the top part of the table, then goes down from there, instead of grabbing the top of the table on the second page

    1
  • Avatar
    Scott Chau

    Might be better if I could see your project but did you make sure you make the elements in your Header and Footer group set as Required?

    0

Please sign in to leave a comment.