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: 
kdmarkee
Specialist
Specialist

NP 17 - Understanding Cycles

I'm hoping to get some clarity regarding cycles in NP. 

My scenario is this:

I'm running NP 17.5, QV 12. 

I have a report that cycles on a [Group Key] where the possible values are -1, 1, 2.  I have a Publish Task Filter in place that makes it so that the only reports that technically should generate are for keys 1 and 2.  How would I bypass the cycle trying to generate a report for key -1?  I believe that is what is causing my task to fail because it doesn't find any report data for that key because the task filter rightly makes it as such.  Can I bypass that key when NP does the cycling through the key with a Condition on my Publish Task, --OR-- maybe by another Filter on my Publish Task, --OR-- do I have to establish a new field (ie, [NP Group Key], let's say) in my script and QVW where that key would have a null value for this new field (and if it is null does the cycling functionality just ignore it or will that also fail)?

Hope this makes sense what I'm after here.  Thanks.

5 Replies
Ruggero_Piccoli
Support
Support

Hi,

You can simply remove the task filter so the cycle will use all values and creates the report also for -1.

To better understand how filters work please check the page https://help.qlik.com/en-US/nprinting/November2017/Content/FiltersCycles/StaticDynamicFilters/Static.... It explains the rules about filters application.

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
kdmarkee
Specialist
Specialist
Author

I need the task filter so the report only shows the info I need within each of the group keys that I'm cycling through.  What I don't understand or how to solve for (assuming this is causing my task from not completing), nor does the online help me here, is if after the result of the task filter there is no data to show for a group key value within my data model, does that in fact cause the cycle to fail, and if so how does one get around it?  I feel like I'm stuck between a rock and a hard place and nothing "creative" I try seems to get this working for me.  Thanks.

Anonymous
Not applicable

Hi Kris,

If I have correctly understood your issue, then unfortunately I don't think there is a proper way to force specific values in a field using the cycling method when creating a report "task" in the report section of NPAC.

I can suggest you a work around which shouldn't give you too much effort in your case.

You can split your task/report into two, using two different filters setting respectively to value "1" and value "2" on your [Group Key] field and then apply them accordingly to your two tasks/reports and disabling cycling method in both.

Yes, it's not very flexible and dynamic but that should do the work and generate and distribute two different reports to your recipients.

Please let me know how you go.

Regards,

kdmarkee
Specialist
Specialist
Author

Thanks for the response.  I think that maybe I need to better clarify my filter in this scenario as I'm afraid that maybe people are thinking that my filter is ALSO leveraging the [Group Key], which is not the case.  My task filter uses a field like this:  [Eligible Row] = Yes.  In my script, an eligible row has been defined as a date 7 days ago and [Incident Missing] = Yes. 


[Eligible Row] = Yes causes data rows for Group Keys 1 and 2, but there are no rows associated to Group Key -1 with this filter.  This scenario seems to cause my task to fail...have I assumed correctly....will this cause the Cycle on [Group Key] to fail?  Thanks.

Ruggero_Piccoli
Support
Support

Maybe I have understood.

Please upgrade your installation to February 2018 and, when it will be available, to April 2018. We are doing a tremendous effort in order to avoid failures in case of inconsistent filters. I suppose that the filters combinations is generating some empty or void dataset. Void dataset means that some filters are generating an impossible combination (for example a filter select month=January and another Quarter=Q2).

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.