Feature Request: Graceful Handling of Zero-Result Page Iterations in Scheduled Jobs

Targit's page iteration feature, available in the Pages options of a report layout, allows a report to be run once per member of a selected dimension,  generating one page (or output) per iteration. This is useful for building dynamic packages that cover, for example, every store in a region or every product in a category. and the ability to manage this like a cross tab (sort, top X, etc) is very useful. 

However, when the dimension members driving the page iteration return zero results for a given pass, the scheduled job errors out rather than skipping that iteration and continuing.

The problem

Zero results for a given iteration member is a valid business state, not a data error. The current behavior treats an empty iteration as a failure, which breaks the full scheduled job.

Use cases

  • Conditional deep-dive reports: A report is built to surface products meeting specific conditions. Not every Store (the dimension the package runs on) will have qualifying products in every period. The iteration for that Store should simply produce no output — not crash the job.
  • Threshold-based visibility: A visibility agent suppresses rows below a sales threshold. If no products for a given Store exceed the threshold, the page iteration has nothing to render. The expected behavior is to skip that page, not error.

Requested behavior

When a page iteration returns zero results for a given dimension member, the scheduled job should skip that iteration, continue to the next member, and log the skip as informational rather than as an error.

4

Comments

2 comments
  • This would be instrumental in saving hours of time from our team without having to manually run each package iteration because the scheduled job times out. 

    To be able to run the same package and iterate for each division, for many groups or item sold would be very helpful.

    0
  • Hi Amanda,

    Your description of empty result behavior does not match our expectations. So it might be something unique to how you use reports in combination with iterations.

    Please raise a Support ticket with our Support team, so they can dig into the exact issue with your case.

    Link to official support: https://www.targit.com/company/support

    BR / Ole

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post