3 Replies Latest reply: Jun 15, 2016 11:36 AM by Steve Lord RSS

    QV NPrinting, Cycle question - multiple connections

    Steve Lord

      Hi All, If I have three different qlikviews connected to an nsq.  All three have the field Client, and I want to create a single report for each client on my client list.

       

      Can I use Cycle for this?  If so, how.  If not, is there another efficient approach I can take besides creating many reports or merging large qlikviews?

       

      or should I create each client report separately and have the three dashboard's client filters applied? (much quicker for now but less scalable)

       

      or should I (try to) create a hybrid qlikview and Cycle the client field on that?  (a heavy undertaking for now, but more scalable.  A couple of the documents are hefty, and though much of their source data is the same, it is aggregated differently in script for reasons.  So I wouldn't easily be able to consolidate overlap, and I would end up with a somewhat huge document at the end.)

       

      Thanks in advance!

       

      Edit: Marking this presumed answered.  Ultimately I noticed one of the qlikviews had all but a few of the data points I needed, so I did a bit of work to bring those last few data points into it.  Now I only need the one qlikview and can use the cycle feature to cycle through the list of clients I flag to create reports for them.  'Bit of work' was four hours, but it's a one-time setup that makes this reporting job extremely scaleable.  Now I just need one report per unique report template being used, and not one report for every client/template combination.

        • Re: QV NPrinting, Cycle question - multiple connections
          Daniel Jenkins

          Hi Steve,

           

          Since you have the same field (Client) in all three connections, it is possible you could benefit from QlikView NPrinting multi-doc features: QlikView NPrinting 16 Tutorials - Multi-Document

           

          HTH - Daniel.

            • Re: QV NPrinting, Cycle question - multiple connections
              Steve Lord

              Yes!  That's it.  Linked Field Entity between multiple qlikview sources. The tutorial you linked me actually goes as far as connecting multiple qvws to a report.  But at the end, it links to another tutorial about how to setup a linked field entity between themultiple connections.  (Year on one qvw and sales year on another qvw in the case of their example, client in the case of my need.)  The linked field entity can be used to setup either a union join (all values on all sides) or an inner(?) join (only the intersection of values that exist on all sides) of the field the qvws have in common.

               

              How to Use Linked Fields with Keep All Values

               

              That said, I've already finished channeling the last few data points to the one qvw and probably would've had to for other reasons anyway (it's shaping up to be a sleeker 'version 3' of a large 'version 2' dashboard.)  If the source data for the qvws isn't just the same database, but includes flat files and such, you'll want to comb through and make sure the field values in the linked field entity are consistent across the qvws too   For instance, one dashboard had client ACME and another had Acme, and I was writing mapping tables to reconcile those kinds of differences between the respective qvws.

                • Re: QV NPrinting, Cycle question - multiple connections
                  Steve Lord

                  Other likely case for consolidating to a single dashboard might be if 70% of your clients use TemplateA, 19% use TemplateB, 1% use TempateC and 10% don't need a report.  I think I will be creating flag fields for the different templates to identify which clients I want to use template a, b, c.  Then on the three reports I make, I'd have the first cycle through the clients present on the TemplateA field's list, then the second report cycle through clients on TemplateB.  I'd use the actual clientnames in the values for the template fields, so they can come through in the field value position on the report's file name.

                   

                  Example Client nprinting report Template flag table:

                  Client TemplateA TemplateB

                  Acme Acme

                  Bacme Bacme

                  WidgetCo             Widgetco

                  Something            Something

                  Another

                   

                  And cycling through TemplateA field values would produce reports for Acme and Bacme, while cycling through TemplateB field values would produce reports for Widgetco and Something.  And no report would be generated for client Another.  At least, I hope that will work out when I do it.  It should.   (Reporting team gave me a list of which clients need this same 12 metrics, and which clients need these other 10 metrics, and which clients need these other 30 metrics.  And I will be making one template for each group of clients.)