topic Re: Row number or column number cannot be zero in Qlik NPrinting

Row number or column number cannot be zero

sogloqlik — Wed, 23 Nov 2022 13:50:38 GMT

Hi.

I have created an HTML Report with nested levels and a table in the bottom level. The report is sent by email to our sales managers with a user filter for each one of them. Some of the managers get an Email with an error message. For those mangers, the task log shows the following message: "Row number or column number cannot be zero".

What does it mean?

Thx.

PS - We are running NPrinting May 2021 With QlikSense May 2022

Re: Row number or column number cannot be zero

Frank_S — Wed, 23 Nov 2022 20:34:33 GMT

Check for object filters that you may have inserted in the NP report designer.

Object filters (and other filters such as task, report filters) may conflict with user filters when the same dimension is used as a filter.

If you don't need the object filter (ie if you have a user filter using the same dimension), then the table or image object filter should be removed.

Further, keep in mind that May 2021 NP is not certified as compatible with May 2022 Qlik Sense.

https://help.qlik.com/en-US/nprinting/May2021/Content/NPrinting/DeployingQVNprinting/System-requirements_engine.htm

See NP Qlik Sense compatibility table in the link above.

Qlik NPrinting should generally be equal to or greater than Qlik Sense.

Kind regards...

Re: Row number or column number cannot be zero

Ruggero_Piccoli — Thu, 24 Nov 2022 08:36:22 GMT

Hi,

The filter applied to the user returns an empty dataset. You can check this by applying the same filter in the source Qlik Sense app.

I suggest you evaluate adding a condition associated with the report in the task that checks if the table in the deeper level has data. Refer to https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/ReportsDevelopment/Conditions.htm

Please also note that each distinct combination of upper levels is a filter that could cause an empty table on the deeper level. Check your data in particular for users with the error.

Another suggestion could be to replace the nested levels with a pivot table in the source Qlik Sense app. This will speed up the report generation because each value of the nested level is a filter that needs to be applied and wait for the export of the table.

Best Regards,

Ruggero

Re: Row number or column number cannot be zero

sogloqlik — Thu, 24 Nov 2022 15:17:26 GMT

Hi.

Thank you both for your replies.

I should add more details:

I tried to reproduce the problem for those sales managers, and I got the expected result without any problem.

There is no object filter, only task filter (Date) and user filter (sales manager).

The report is being sent to me also and I got the same error from the task - I am and administrator without user filters.

There is the compatibility issue, I will check it.

I will look for any conjunctions between the filters.

Replacing the nested levels with pivot is less desirable. I barely managed to produce pivot with html (with your help Ruggero) .

Are the more things I should check?

Re: Row number or column number cannot be zero

Frank_S — Thu, 24 Nov 2022 16:04:08 GMT

Remember that you are not in a supported state so that could be the issue.

However, if you wish, you can share a sample QVF and NP report here and we can try to reproduce the issue.

We will also need to know exactly how you constructed your publish task including conditions used (condition definitions if any, etc) so we can attempt to reproduce.

Kind regards...

Re: Row number or column number cannot be zero

sogloqlik — Thu, 24 Nov 2022 17:06:23 GMT

Hi.

After further investigation I found that indeed those errors occur when there is a value in the lower level, but the corresponding table is empty.

But now I'm facing a new problem: I built two small "Filter" tables, one for each level but after reloading the metadata again, when I'm trying to add them to the levels, I can see only one of them (I can both of them if I'm trying to add them to the tables)
🤔

Re: Row number or column number cannot be zero

Ruggero_Piccoli — Fri, 25 Nov 2022 10:00:24 GMT

Hi,

After reloading the metadata remember to close and re-open the Qlik NPrinting Designer because it reads the metadata only on opening.

When you do a right-click over the Levels node, you will see the list of only the objects that are of supported types. If you do not see a table check it in the source app and be sure it is a straight table and of the same type of the table, you can see.

Best Regards,

Ruggero

Re: Row number or column number cannot be zero

Lech_Miszkiewicz — Fri, 25 Nov 2022 12:40:20 GMT

Hi,

I guess the reason you dont see it in Levels is that you have probably used calculated dimensions which will not work. This is documented on https://help.qlik.com

cheers

Re: Row number or column number cannot be zero

sogloqlik — Sun, 27 Nov 2022 13:59:28 GMT

Thx for the answers.

The Tables are the same, the dimensions are not calculated, both show unique values, and it goes without saying that the designer should be closed after refreshing🙂
The only difference between the two tables is that the visible one contains values from a Dim table in the Qlik model (Where every value is itself is unique) while in the second table the dim values are from the fact table (not unique).

Could that be the problem?

Re: Row number or column number cannot be zero

Lech_Miszkiewicz — Sun, 27 Nov 2022 22:29:26 GMT

no - that shouldnt be a problem.

Are you using native Qlik Sense straight table? or maybe pivot table or some sort of extension? Are there any unsupported objects with things like: "show column if"?

cheers

Re: Row number or column number cannot be zero

sogloqlik — Mon, 28 Nov 2022 07:11:11 GMT

Hi.

The Table is native Qlik Sense straight table - the exact same table as the visible one, the measure is the same, only the dim is different. I tried to create it again in the same sheet, different sheet, in a different NP report - nothing, So i guess it has something to do with the Dim itself.

Cheers.

Re: Row number or column number cannot be zero

Ruggero_Piccoli — Mon, 28 Nov 2022 12:22:57 GMT

Hi,

Please check if you are using not supported, or partially supported, objects listed at https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/ReportsDevelopment/Qlik-objects-supported-NP.htm#anchor-2

Be sure to:

create the new straight table in Qlik Sense by using only supported objects
refresh the connection cache
close and re-open the Designer because the cache is read-only on opening

Then you should be able to see the new table in the lists.

Best Regards,

Ruggero

Re: Row number or column number cannot be zero

sogloqlik — Mon, 28 Nov 2022 13:12:14 GMT

Thank you Ruggero for your answer.

Well, problem solved. and the reason is quite annoying considering the time I have spent:
The problem was that the dimension had the '=' sign before the field.. I guess it was a table dim (which works fine) and someone saved it as a master item and the system interpreted it as a calculated dimension.

Again, Too many hours spent....😡

Motty

Re: Row number or column number cannot be zero

Ruggero_Piccoli — Mon, 28 Nov 2022 13:12:33 GMT

Hi,

Thanks a lot for sharing the solution: it will help many other readers in the future!

Best Regards,

Ruggero

Re: Row number or column number cannot be zero

Lech_Miszkiewicz — Mon, 28 Nov 2022 13:37:05 GMT

Like i said-calculated dimension, and yes, = sign in front of the field name makes it calculated dimension (also in master items as well as in the dimension in table). = sign appears as soon as you click on fx icon so it is easy to miss that if you dont pay attention.
I am glad you got this sorted though.