QlikView App Dev

[Michael_Tarallo]

Hello Qlik Community,

We are excited to announce the release of the QlikView Governance Dashboard and QlikView NPrinting 17.

• The QlikView Governance Dashboard is the most downloaded resource from our Qlik Market.  This free QlikView application delivers a 360 degree view of any QlikView deployment and it is utilized by QlikView administrators to analyze and optimize how their QlikView environments work.

• QlikView NPrinting 17 is the next generation of the NPrinting product line.  It features a new web-based client, a self-service subscription portal for users, and enhanced security and scalability for the enterprise – based on a new multi-threaded and multi-node architecture.  With QlikView NPrinting 17, customers can utilize QlikView for both analytics and reporting, eliminating the need for redundant systems.

To learn more, see what our resident Jedi of BI PeggySue Werthessen has to say in her latest blog: Qlik Loves QlikView! | Qlik

and watch these brief videos.

QlikView Governance Dashboard in 60 Seconds

NPrinting 17 in 60 Seconds

[luciancotea]

Hi Michael,

Great news.... care to comment about the missing features? Are the projects developed in v16 compatible with v17?

The following QlikView NPrinting 16 features are not yet availabe in QlikView NPrinting 17:

• On-demand

• Conditional reporting

• Recipient import wizard

• Dynamic report naming

• FTP destination

• Cycling reports

• Variable filter

• Linked fields

• Load template

We plan to add them in upcoming releases.

Upcoming releases of v17 or in v18?

[Anonymous]

I am wondering the same thing as Lucian. Excited to upgrade because of a number of new features, but cannot  upgrade if Cycling reports/Variable filter is not available.

When are the features documented as missing planned to be added to future releases?

And how do v16 projects react when upgrading to v17?

[Michael_Tarallo]

Hi Guys - I'll find out for you.

Mike

[Stephen_Jasionowski]

All -

The feature gaps from NPrinting 16 are expected to be closed in releases this year.

As far as migrating projects from NPrinting 16 to NPrinting 17, as of now, you can only import report templates. There is an export project button in the NPrinting 16 Designer client that will produce a .zip file that contains all the templates for that NPrinting project file (.nsq). But it is important to note that only the template itself gets imported into NPrinting 17.

This means:

• Any filters that were applied to the report in NPrinting 16 will have to be re-applied
• Features such as cycle or conditions that are gaps as part of the 17.0 release cannot be applied at this time

Since only the template is imported (this takes place in the Designer client launched from within the NPrinting 17 web interface), things like schedules, tasks, recipients, etc. need to be redefined in the new version.

I do not have any information at this time as to whether future releases will support more than just the template import.

[luciancotea]

Stephen Jasionowski <span class="icon-status-icon icon-employee" title="Employee"></span> wrote:

All -

The feature gaps from NPrinting 16 are expected to be closed in releases this year.

     Then why don't you just close all the gaps and release a complete product? Is it pressure from the shareholders to release something, no matter what?

[louiswinter]

Lucian,

Do you have a secondary list of NP16 features that are not currently in NP17, and that are not on the priority list?  In addition to the "Reload task" to reload a .qvw and "External task" files to trigger jobs and tasks, what else is missing that isn't on the above list?  Also, is there a tentative timeframe for when the secondary gaps will be resolved?

Louis

[luciancotea]

Louis,

It's not me you should ask. I have the same questions.

Lucian

[louiswinter]

Michael,

Do you have a secondary list of NP16 features that are not currently in NP17, and that are not on the priority list?  In addition to the "Reload task" to reload a .qvw and "External task" files to trigger jobs and tasks, what else is missing that isn't on the above list?  Also, is there a tentative timeframe for when the secondary gaps will be resolved?

Also, I saw a thread indicating that .nsq files will no longer be used.  We currently develop our NPrinting reports on a segregated development server using direct .qvw file connections.  When the .nsq file is deployed to production we run a custom program we wrote against the file that changes the connections from local files to server (qvp).  Without .nsq files this obviously won't work, do you have any thoughts on how we will be able to develop in a different environment than production with NP17?

Louis

[squeakie_pig]

Are there any plans in the works to update NPrinting so it is compatible with versions of Office > 2013?  You can't buy 2013 anymore so anyone who doesn't already have it can't use NPrinting to export to office format.