Troubleshooting your migration

You are trying to import a QlikView NPrinting 16 project with the .nsq file saved in an old format.

To solve:

1. Open the original .nsq file in a recent QlikView NPrinting 16 version.
2. Save it, even if you did not modify anything, to force the conversion to a supported format
3. Export the project again.

You are trying to import a QlikView NPrinting 16 project without any connections.

To solve: Check the connections in QlikView NPrinting 16, and export the project again.

You are uploading an exported project file (.zip) that does not contain an .nsq file.

To solve: Export the project again in QlikView NPrinting 16.

The import of a variable filter failed. Check that the variable {name} exists in the related .qvw.

To solve, try one or more of the following:

• Create the variable in the .qvw and refresh the connection cache.
• Modify the filter, in order to avoid using the variable.
• Delete the filter.

Linked fields are not supported in Qlik NPrinting November 2019 or newer.

To solve: Manually modify the filter to use the original fields from different connections. The filter will work as expected, but can not be applied as a level, page, or cycle.

Bookmark filters are not supported by Qlik NPrinting November 2019 or newer.

To solve: Manually modify the filter to recreate the bookmark using the original fields.

The QlikView lock field option is not supported in Qlik NPrinting November 2019 or newer.

To solve: Manually update the created filter.

QlikView NPrinting 16 filters that use the same field more than once are not supported in Qlik NPrinting November 2019 or newer.

To solve: Manually update the generated filter.

QlikView NPrinting 16 filters that use the same variable more than once are not supported in Qlik NPrinting November 2019 or newer.

To solve: Manually update the generated filter.

You are trying to import a filter without field values, which does not have the Clear all selections option flagged.

To solve: Manually add the field in the newly created filter.

The connection to the field {name} does not exist in the imported QlikView NPrinting 16 project.

To solve, try one or more of the following:

• Manually update the imported filter.
• Delete the filter.
• Update the QlikView NPrinting 16 project, export it, and import it again.

The import of the filter {name} associated with the report failed because the filter was not found.

To solve: Manually create the missing filter.

The import of the filter {name}, used in the report as an object filter, failed.

To solve: Manually create the missing filter, and add it as an object filter.

The import of the condition {name} associated with the report failed.

To solve: Manually create the missing condition, and add it to the report.

In Qlik NPrinting 19 November or newer, you cannot add the value of a field to the report file name if it is different than the field used in the cycle.

To solve: Manually modify how the report file name is created using supported dynamic naming features.

See: Cycling your reports and Dynamic report names.

An entity is using the filter {name} that has errors or warning messages.

To solve: Resolve the errors or warning in the filter {name}.

The connection {name} of the field {field} used in a cycle is missing.

To solve: Manually add the cycled field.

The connection {name} to the variable {variable} used in dynamic naming is missing.

To solve: Manually update the dynamic naming configuration by adding the variable.

The QlikView variable {name} used in dynamic naming is missing.

To solve: Manually update the dynamic naming configuration.

The type of the variable {name} used in the imported dynamic naming configuration is not supported.

To solve: Open the report and edit the dynamic naming configuration.

The QlikView object {name} used in the report template is missing.

To solve: Recreate the object in the source .qvw and regenerate the connection cache.

A generic error occurred while reading a QlikViewentity. The error exists the imported QlikView NPrinting 16 project.

To solve:

1. Open the entity that generates the error.
2. Update the entity and make sure it is working properly.

The report template file is missing.

To solve:

• Check that the template file is present in the source QlikView NPrinting 16 project. It is a file-based system, so the template may have been deleted from the original templates folder. In this case, you must retrieve it from a backup or recreate it in the Qlik NPrinting installation.
• Check that the QlikView NPrinting 16 report contains the correct path to the template included the filename. The syntax could have been modified to an incorrect value.
• If you find the file in the QlikView NPrinting 16 templates folder, you can manually create the report in your Qlik NPrinting installation and use it as custom template. Then:
  • Open it in the Qlik NPrinting Designer and add the needed QlikView entities in the treeview, or
  • Export and import the QlikView NPrinting 16 project again, and verify the template is correct.

The report template conversion failed.

To solve:

1. Open the template in Qlik NPrinting Designer.
2. Solve the error messages that appear.
3. Click on Save and Close. This will force the conversion to run again.

Some entities used in the template are missing from the connection cache.

To solve:

1. Open the template in Qlik NPrinting Designer to get a detailed list of the missing entities.
2. Solve the list by creating the missing entities in the source .qvw document. Or remove them from the template.
3. Regenerate the connection cache.

These errors may also appear in the QlikView NPrinting 16 project. For example, if the entities were deleted from the .qvw, but still used in the template. In this case:

1. Solve the errors in the QlikView NPrinting 16 installation.
2. Export and import it again.

The imported condition {name} used in a report in a task has warning or error messages.

To solve: Verify and correct the listed errors.

The connection {name} used in the imported condition is missing.

To solve: Manually update the condition.

The imported condition operator {name} is missing.

To solve: Update the condition by setting a supported operator.

The values option {name} used in the imported condition is missing.

To solve: Open the condition and update it.

The QlikView variable {name} used in the imported condition is missing.

To solve:

• Change the condition by using an existing variable.
• Create the variable in the source .qvw and refresh the connection cache.

The QlikView chart {name} used by the imported condition is missing.

To solve: Create the chart in the source .qvw and refresh the connection cache.

The filter {name} used in the imported task is missing.

To solve: Manually create the filter and associate it to the task.

An entity is using the filter {name}, which has errors or warning messages.

To solve: Resolve the errors or warnings in the filter.

You are trying to use the report {name}, which has warning or error messages, in a task.

To solve: Open the report {name} and correct the errors.

The report {name} used in the imported task is missing.

To solve:

1. Check the import logs to see if there was an error during the import of the report.
2. Create the report in your Qlik NPrinting November 2019 installation from scratch. Or use the QlikView NPrinting 16 template as custom template.

In Qlik NPrinting November 2019 or newer, you cannot add the same report with the same output format and the same quality more than one time for each task. Only the first report is imported and the rest will be skipped.

Some output formats (like Word documents with macros .docm and PixelPerfect reports as .csv) are not supported by Qlik NPrinting November 2019 or newer.

To solve: Add the report to the task and select one of the supported output formats. See: Report output formats.

You are trying to import the report {name} in a task with an unsupported output format {format}.

To solve: Add the report to the task and select one of the supported output formats. See: Report output formats.

Color is the only supported mode in Qlik NPrinting November 2019 or newer.

Report multi-paging is not supported for the report {name}.

The use of custom separators is not supported in Qlik NPrinting November 2019 or newer. They will be replaced by commas.

Custom page ranges are not supported for the report {name} in the task.

Qlik NPrinting November 2019 or newer does not support certain email body tags.

To solve: Update the email body accordingly. See: Planning your migration.

You cannot use an external HTML file as an email body.

To solve: Copy the content of the HTML file and paste it in the email body editor.

External email attachments are not supported.

Email footer images are not supported. You cannot add them manually.

To solve, try one of the following:

• Edit the email body by embedding the image
• Create an HTML body text with the image.

You cannot create an archive containing the compressed reports.

To solve: Send reports uncompressed.

'Low' and 'Medium' report quality are not supported.

To solve: Manually update the quality setting. See: Image quality.

Qlik NPrinting November 2019 or newer cannot send generated reports directly to printers.

QlikView NPrinting 16 destinations are not imported, you must add them manually to the imported tasks.

QlikView NPrinting 16 destinations are not imported, you must add them manually to the imported tasks.

QlikView NPrinting 16 destinations are not imported, you must add them manually to the imported tasks.

QlikView NPrinting 16 destinations are not imported, you must add them manually to the imported tasks.