installing development version

[daveatkins]

I need to set up a developement version of nprinting for testing. How does one license that without breaking the existing server's licensing?

[jwjackso]

We purchased a separate license for our test environment.  We use the test environment to validate patches, security roles, active directory import tasks, etc...

The NPrinting developers actually develop their reports in the production environment.  The developers do not have access to create TASKS and cannot distribute a report.  Once a developer has created a report, as an admin, I will create a task and assign the developer's group to the task.  This allows the developer, who only has the ability to run a task, to test their report.

Once the report has been validated, I will add additional groups to the task and create a trigger to distribute the report.

There was much discussion of the pros/cons of developing in production NPrinting versus migrating reports from dev/test to prod.

[BairStrokes]

Using MSExcel 2007 with NPrinting 16 against Qlikview 12. Upgrading is doubtful.

I'd be applying changes to the spreadsheet template. Then, to test, I request a preview with a preset limited report filter.

Then Excel crashes, NPrinting loses its connection, and crashes the template editor, throwing away the changes.

I have resorted to saving and closing every single change, combined with off-site source control, just to limit the damage these crashes cause.

It's stifling my production speed.

Did you encounter this? If so, did you fix it? How?

[daveatkins]

similar use case for us; development is fine to use the production server, but I have a developer who wants to install something on the server and I don't want to risk that, so I asked her to test it first on a development server. Will see how we can get a license for that I guess.

[Ruggero_Piccoli]

Hi @daveatkins ,

Contact your Qlik reseller or salesman to have a development license.

Best Regards,

Ruggero

[Ruggero_Piccoli]

Hi @BairStrokes ,

Please open a new conversation for a new question. Note also that 16.* is no more supported so you can upgrade to latest 16.10 and check if you still have the issue. If it appears also with it you have to upgrade to 17+ (February 2021 right now).

In the new post add also all details that will let us to understand what is happening.

Best Regards,

Ruggero