6 Replies Latest reply: Nov 17, 2017 8:39 AM by Grant Perkins RSS

    Footer not attached to detail data from previous page

    Matthew Lee

      Hello everyone,

       

      I am having an issue with attaching Footer information to the Detail dataset from a previous page. This is how the data is structured.

       

      Previous Page

      Client name [Header]

      Transaction data [Detail]

      Transaction data [Detail]

      Transaction data [Detail]

      Transaction data [Detail]

      Transaction data [Detail]


      Next Page

      Client name [Header] - same client as previous page

      Transaction data [Detail]

      Transaction data [Detail]

      Transaction data [Detail]

      Transaction data [Detail]

      Summary data [Footer]


      I need the Footer to attach to the Detail from the previous page because the Detail information belongs to the same client but I am guessing Datawatch separates two data sets because they are divided by the Client name reappearing in the Next Page. Is there any way to circumvent this issue? Your help would be much appreciated!

        • Re: Footer not attached to detail data from previous page
          MelaSarenas _

          Hi Matthew,

           

          AFAIK, footers will be attached to all detail rows above it until it reaches another footer row.  So for your example, a straightforward creation of a Footer template will extract footer fields for each detail row even though the detail row is on the previous page.

           

          Footer templates will work the same way as Append templates but on opposite directions.  Appends goes down the detail rows until it reaches another Append row, Footers goes up the details rows until it reaches another Footer row.

           

          HTH

          Mela

            • Re: Footer not attached to detail data from previous page
              Matthew Lee

              Hi Mela,

               

              That's what I thought too but the Footer actually doesn't extend to the previous page and that's where I am having a trouble. I think it's because the page header starts again at the top of the Next Page and that's stopping the footer from attaching to the Detail rows from the previous page.

               

              Thanks,

              Matt

                • Re: Footer not attached to detail data from previous page
                  MelaSarenas _

                  Hi Matthew,

                   

                  Maybe your Footer Template has a clearing template defined to it?

                   

                  Mela

                    • Re: Footer not attached to detail data from previous page
                      Matthew Lee

                      Hi Mela,

                       

                      Great point. I actually did have a clearing template set on Page Header and removing it solved the issue for this particular section of the extract. However, I remembered why I defined the clearing template in the first place (sorry it's been a while since I built this model). There are client transaction data throughout the report that does not have the Footer and they shouldn't have the Footer value attached from the next page or next client data with Footer information. I guess there is no way to selectively choose when to attach Footer values right?

                       

                      Thank you for your prompt response by the way. It's been very helpful.

                       

                      Matt

                        • Re: Footer not attached to detail data from previous page
                          MelaSarenas _

                          Hi Matt,

                           

                          Yes we can't select to which detail row a footer is attached.  Hope you find a resolution.

                           

                          Mela

                          • Re: Footer not attached to detail data from previous page
                            Grant Perkins

                            Matthew,

                             

                            You could try looking for something that would allow you to successfully trap the footer but effectively trap a blank footer on those pages where there is no footer and none required.

                             

                            However given the original problem of the detail data crossing pages that may not be so easy.

                             

                            Plan C would be to capture a footer for all pages but have a way to identify the record from pages where no footer should be in place.

                             

                            If that is possible you could look at creating  context sensitive calculated field that copies the footer when it should be present and is blank when it should not be present. Then use the calculated field as the proxy for the footer.

                             

                            Difficult to know if it will work  - much depends on the report layout. Probably worth considering though.

                             

                             

                            Grant