Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
pradosh_thakur
Master II
Master II

Issue Meta data reload in Nprinting

Hi All,

i am using QV 12.20 (Nov 2017) and Nprinting 17.6 (November 2017)

If reloaded the meta data using local connection i can see all the fields (around 700) if through qvp(server) connection i can see only 180 fields.

i disabled all the one selected value,sheet event trigger , document event trigger. there is no alternate states no section access, reduction based on section access uncheked.

Nprinting and Qlikview are on different servers. The issue remains. I need server connection as on-demand fucntionality is required.

please advice if i am missing anything.

sjwlech_miszkiewicz

regards

Pradosh

Learning never stops.
1 Solution

Accepted Solutions
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

‌understand!

all good then-lets see how it goes after an upgrade.

good luck

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.

View solution in original post

9 Replies
blaise
Partner - Specialist
Partner - Specialist

Before the gurus can answer, how may fields do you see when opening the qvw document in Qv Desktop on Nprinting server with "Open in Server" using NPrinting service account?

pradosh_thakur
Master II
Master II
Author

I used the same qvp connection string to open the qvw and i can see all the fields.

Learning never stops.
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

well - interesting.

I can only think of all bugs we had in previous versions so please upgrade at least to version Feb or April 2018 - they both have different methods of generating metadata so it could probably fix the problem.

I do not think there is anything else i can suggest at the moment since you are saying that there is no section access and app is not reduced by publisher or anything similar.

else - open support ticket.

regards

Lech

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
pradosh_thakur
Master II
Master II
Author

Hi Lech,

If the document is not supported then the entire dataset(metadata) will not be fetched . so the no of fields i should get in n printing should be same.

In server:

Another interesting thing is if i add a new table box with let say column "A" (which is not getting fetched IN SERVER CONNECTION) , i can see the object in n printing. but if i use that object i get error while report generation(aborted).

Learning never stops.
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

i am not talking about document - i am talking about the way particula version of nprinitng works.

it is your choice at the end - but given that i also had problems with previous versions of NP i can only suggest first to do an upgrate to eliminate any known bugs and issues.

It is up to you if you would like to follow my suggestion.

thanks

Lech

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
pradosh_thakur
Master II
Master II
Author

i have asked for an upgarde already Lech ..

I was not questioning you on the solution but humbly asking a query that in Qlik manual there are certain criteria with which a document becomes unsuitable for Nprinting which can result in not getting the complete data set. In these case too document should fetch all the fields (i counted it in the page option in the template editor) in both server as well local connection.

thanks

Pradosh

Learning never stops.
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

‌understand!

all good then-lets see how it goes after an upgrade.

good luck

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
pradosh_thakur
Master II
Master II
Author

Hi Lech,

Turned out it was a bug with Qlik 17 which got fixed in April release 2018. Now its working fine after the upgrade.

ThankYou.

Learning never stops.
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

great

told you - always keep it up to date with NPrinting - new versions are there for a reason!

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.