NPrinting 17 June 2017+: Good Practise recommendations when working in TEST and PROD environment? And Naming Conventions?

[jblomqvist]

Hello all,

Can anyone suggest good practises when it comes to NPrinting and June 2017 onwards for the following:#

1. We have a TEST and PRODUCTION environment so how to migrate reports from Test to Prod
2. Naming conventions when it comes to various NPrinting tools and build reports from QlikView
3. Any other good practises when developing NPrinting reports in an Enterprise organisation

Thank you in advance

[JustinDallas]

I know this is late, but I do know that one of the issues I've had with is naming things sufficiently enough that I can figure out where they come from.  One of the things I do is I always try to include small amounts of metadata in the names of my objects.  Generally naming things beginning with the stream, app and then the component/filter params/report name.

It helps me find things months after I've created them, and it helps when you sort alphabetically and things are grouped by report by proxy.

Finance > Microsoft GP Payables > Fuel Filter (this points to a stream named Finance, an app named Microsoft GP Payables, and is a filter based around fuel providers)

AR > Microsoft GP Receivables > Late Report (this points to a stream named AR, an app named Microsoft GP Receivables, and is a report).

Maybe some other people have other ideas.