27 Replies Latest reply: Sep 1, 2017 3:56 AM by Ruggero Piccoli RSS

    Nprinting 16 or 17 for Qlikview

    Frédéric Villemin

      Hello,

       

      We have just bought NPrinting and I begin having installation problems with 17.3. I remember the times when installation a Qlik product was easy, it's not the case anymore !

       

      Last year, one guy in Qlik had adviced me to stay with v16 because the v17 was not ready.

       

      I'm afraid I will lose time trying to install v17.3, making ticket because the installation doesn't work correctly, and I would like to know if people are still using v16 ?

       

      If I'm only using Qlikview to make reports, is it a good idea to stay in v16 while waiting to have a good v17 or is the v17 far better than v16 and I should go to it because everything missing has been added and it works great ?   Honest advices please

        • Re: Nprinting 16 or 17 for Qlikview
          Robin Hausdörfer

          I tried 17.2.1 open-minded, never tested 17.3.

          The installation itself was problem-free.

           

          Besides a few bugs I found within 1 testing week,

          there are some NP16 features missing, that  I use extensively:

           

          - trigger reload for local qvw file

          - clone elements in web interface for testing (filter, task, report, ...)

          - using QV variables within mail text and subject line

           

          Another important fact:

           

          The main difference between 16 and 17 is that in 17 everything will be stored within one repository.

          So you are not able the make a copy of an nsq file like you did in 16 and manipulate it for testing reasons.

           

          ... just my personal thoughts

          • Re: Nprinting 16 or 17 for Qlikview
            gareth wilson

            I would recommend installing v17 on its own server without any other Qlik server products and just Qlikview desktop installed.

             

            I would also be aware that in the near future Qlik will end support for v16 so you will have to go through the pain of upgrading everything.

             

            For a new install I personally wouldn't build an estate of reports in a product that is being sunsetted.

             

            Just my opinion though.

              • Re: Nprinting 16 or 17 for Qlikview
                Robin Hausdörfer

                Hi Gareth,

                I absolutely agree. Yes, it basically makes no sense using NP16 anymore.

                 

                But I think that it is very dificult to place, that a newer version of a product supports less features then its predecessor.

                 

                At the moment it is not possible for me using NP17 due to the lack of missing features.

                I was not able to build the same reports in NP17 , regardless of how much time I invested.

                 

                ... just my personal thoughts

                  • Re: Nprinting 16 or 17 for Qlikview
                    Frédéric Villemin

                    Robin,

                    it's exactly the same between Qlikview and Qlik Sense.

                     

                    Qlik had first released Qlik Sense as an upgrade to Qlikview (Qlikview Next). But when a new tool lacks great features, customers cannot forget everything and switch to the new tool .. It became Qlik Sense and they said they would remove Qlikview after a few years. I don't think the same policy exists now as Qlik Sense doesn't fit most users needs

                    • Re: Nprinting 16 or 17 for Qlikview
                      gareth wilson

                      Totally agree Robin as you have invested time and effort into v16  with features v17 doesn't support.

                       

                      Most if not all the missing features are on Qlik's roadmap and I'm sure they will not discontinue v16 support until the new product is at least equal in its offering.

                       

                      However for a new install I would certainly go with v17, you eliminate the possibility of creating new reports with missing features and will continue on a product path that Qlik are investing in.

                       

                      It's also easier to explain to end users that the product 'doesn't do that' rather than 'it did do it but we can't anymore'.

                    • Re: Nprinting 16 or 17 for Qlikview
                      Frédéric Villemin

                      Yes, you're right but I don't have a specific server to do that for the moment. I wanted to install it on the same server my test version of Qlikview.

                       

                      And it's better to start with the newest version, too bad it seems to lack features of the v16 ...

                    • Re: Nprinting 16 or 17 for Qlikview
                      Matus Kelemen

                      Hi Frederic.

                       

                      is the v17 far better than v16 and I should go to it because everything missing has been added

                       

                      No and no.

                       

                      The v17 is not better by any means in terms of report creating. The architecture under the hood changed (to work with sense I assume) and they are slowly catching up with the functionality.

                      Also the new web interface is pain to work with (no copy/paste).

                       

                      We are facing similar decision but we already have a lot of reports created which use some of the functionality that has not been ported yet. We could probably create workarounds if necessary but it would be a lot of work. So we are staying put and hoping that it will be implemented in 17 soon.

                       

                      Your advantage is that you do not have the existing body of work and can start fresh without losing much.

                       

                      BR,

                       

                        Matus

                        • Re: Nprinting 16 or 17 for Qlikview
                          Neil Gulliver

                          Hi,

                          I think it may also be worth noting here that there is no upgrade path between 16 and 17. Also, Qlik announced some months ago that the end of support for v16 will be February 2018.

                           

                          Whilst I have found 16 far more stable and more feature-rich there may be no business rationale to go with anything earlier than 17.

                           

                          Cheers,

                          Neil

                        • Re: Nprinting 16 or 17 for Qlikview
                          Roland Steger

                          Hi,

                          its already a half a year old thread but so far its still relevant:

                           

                          We also bought a year ago Nprinting to replace an very unstable reporting system (Crystal Delivery on old XP machine). But so far we did not really use it, as the version 17 does (still) not fit (all of) our needs. For very simple reports we can use it, but so far many basic features are not there:

                          - the product is called Nprinting but cannot print directly to a printer

                          - more options for scheduled execution (monthly, yearly, etc)

                          - Cycling reports

                          - clone reports

                          - buggy

                          - ...

                           

                          I got the info that the developer team wants to release a new version every 10 weeks. Next should be planned for September 2017. If not anytime soon the needed features come to v17 I need really to think about to use v16. They still releasing new versions (and supporting v12.1 of QlikView) and the support was already extended till December 2018. In my opinion Qlik should publish a roadmap when they plan which features roughly come to v17.

                           

                          Surely its not easy to write such a big program like this from scratch in few months, but still.......

                           

                          Let's hope the next release brings some of our needed features

                           

                          Cheers

                          Roland

                            • Re: Nprinting 16 or 17 for Qlikview
                              Ruggero Piccoli

                              Hi,

                               

                              - cycling reports

                              - import/export (so you can export a report and create a new one from the exported one so it is the same as cloning)

                               

                              are both part of next release September 2017. You can download a technical preview from Qlik NPrinting September 2017 Technical Preview. This is a preview not for production use. The related final version will be publicly available in September.

                               

                               

                              Best Regards,

                              Ruggero

                              ---------------------------------------------

                              When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.

                            • Re: Nprinting 16 or 17 for Qlikview
                              Lech Miszkiewicz

                              I see NP 17 as the product i would go with.

                               

                              I know it goes through difficult days now, but at the end it will be the product Qlik will go with forward. If it is small setup you are thinking about you can start with v16, but i f you are aiming in creating 20+ reports, one day soon yo uwill have to build them all from scratch in NP17. I do not think it is worth extra work.

                               

                              cheers

                              Lech

                                • Re: Nprinting 16 or 17 for Qlikview
                                  Roland Steger

                                  Hi,

                                  yes i am thinking the same and we are still deciding what to do. Normally in QlikView things were growing fast in the past, so probably with NP would be same . Everyone wants new stuff :-)   So we still keep alive our old system as long as possible and start slowly with easy reports in v17. When the time is ready we can move all old stuff to the new system. Our consultant told me the developers want to push a new version every 10 weeks, so something should be expected in near future.

                                   

                                  I read that the swap from v16 to v17 is also not so easy so......

                                   

                                  Best regards !

                                  Roland

                                  • Re: Nprinting 16 or 17 for Qlikview
                                    Frédéric Villemin

                                    Hello Lech,

                                     

                                    You are probably right. But I'm afraid I don't trust Qlik anymore on new products.

                                     

                                    Releasing a V17 of Nprinting without the cycling feature seems incredible for me.

                                     

                                    I'm happy to see that the new version will be released in september and will include everything but I will wait to see if everything works as expected and I prefer doing my 10 reports twice instead of waiting months to have the new version of the tool I bought as good as the previous version.

                                      • Re: Nprinting 16 or 17 for Qlikview
                                        Lech Miszkiewicz

                                        Well. I never thought NPrinitng 17 is the next verion of NPrinitng 16

                                         

                                        To me this comparison is like QlikView and Qlik Sense - they are 2 different product, but both have similar functionalities!!!

                                         

                                        NPrinting 17 is new way of doing stating reporting supporting QlikView and Qlik Sense, but it cannot be considered as the next version of the same product (NPrinting 16), because it is different product.

                                         

                                        On the other note - I think Qlik rushed with NP 17 and released it, when it was not fully tested and ready , but this is different topic.

                                         

                                        cheers

                                        Lech

                                          • Re: Nprinting 16 or 17 for Qlikview
                                            Frédéric Villemin

                                            Haha you are kidding I presume ?

                                             

                                            NPrinting 17 is not the next version of NPrinting 16 ? 

                                            It's a bit easy to say that .. I think customers who have bought NPrinting 16 are still waiting for updates and new features and it seems that Nprinting 17 is here for that. Even if, I agree with you, it uses a new technology and Qlik has rushed with NP 17 and should have tested it.

                                             

                                            It reminds me the first name of Qlik Sense : Qlikview Next. Because it should have been the new version of Qlikview. But when people said that most features of Qlikview were missing from Qlikview Next, it was renamed into Qlik Sense and we've been told that it was a completely new tool.   But at the beginning it was not

                                              • Re: Nprinting 16 or 17 for Qlikview
                                                Robin Hausdörfer

                                                ... 2 different products with the same name...

                                                • Re: Nprinting 16 or 17 for Qlikview
                                                  Lech Miszkiewicz

                                                  no kiding... 2 different products.

                                                   

                                                  I think

                                                  NPrinting 16 is called QlikView NPrinting

                                                  NPrinting 17 is called Qlik NPrinting (except of initial version for NP 17 which was still positioned under QlikView NPrinting).

                                                   

                                                  as I said it is like QlikView and Qlik Sense. Qlik has said (at least to us as partners) that NPrinting 17 is positioned as a new product which will finally catch up with old product and finally can replace v16. Why NPrinting version 16.6 was released? Because it supports QlikView 12.1 and can be used as a supported product at least for another year (i think till Dec 2018). By this time NP 17 should have missing features implemented.

                                                   

                                                  re comment about QlikView Next, from what i remember that was never official name for Sense, as it was only project name for BETA releases of it.

                                                   

                                                  cheers

                                                  Lech

                                                    • Re: Nprinting 16 or 17 for Qlikview
                                                      Frédéric Villemin

                                                      I understand your point but maybe you can understand that customers are not as silly as people can think.

                                                       

                                                      I have bought a licence for NPrinting and have access to a tool called Qlikview NPrinting 16 which is used for making reports out of Qlikview and I also have access to a tool called Qlik NPrinting 17 which is used for making reports out of Qlikview and Qlik Sense and which will replace the first one when all features are copied.  I call that the same tool with different version number and upgraded features in v17.

                                                       

                                                      Apple would just call that "a brand new version rewritten from scratch with incredible new features". That would be better to say that instead of trying to fool people by saying : "no, we knew that removing the cycle feature would be ok because it's a new tool, it's called Qlik NPrinting 17 and people can stay with QlikView NPrinting v16 which is a completely different tool"

                                                       

                                                      The 16.6 release of NP16 is not a proof that they are two different products, it is just a proof that people don't want to use v17 because it lacks features and Qlik has no other solution than to release a new 16.6 to be able to use QlikView 12.

                                                       

                                                      It was the same with QlikView.  11.2 should have been the last version of QlikView, but many customers didn't want Qlik Sense and v12 was released.  They are now two different tools. That's good.

                                                      Maybe what you want to explain to us is that NP16 is the QlikView NP and NP17 is the Qlik Sense (and QlikView) NP. I understand that but maybe they should rename it because it's too complicated for us poor customers.

                                                       

                                                      I understand you are a partner of Qlik, but sometimes I hope it can help them to show their errors. I was in a meeting of Qlik Sense Tour a few months ago and even Qlik people were not happy about the v17 (and all customers I have met were still QlikView fans and NP16 only users)

                                                       

                                                      Let's hope the new version of NP17 will make all customers happy.

                                                • Re: Nprinting 16 or 17 for Qlikview
                                                  Ruggero Piccoli

                                                  September 2017 Technical Preview with cycles can be downloaded right now from Qlik NPrinting September 2017 Technical Preview

                                                   

                                                  You can create a testing enviroment without the need of waiting and test you reports there. Many bugs of the September 2017 TP are already resolved in the version that will be released quite soon.

                                                   

                                                   

                                                  Best Regards,

                                                  Ruggero

                                                  ---------------------------------------------

                                                  When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.