When Page Headers Attach in V14
Hello,
We recently upgraded from Monarch 10.5 to V14. One of my old frequently used tricks was when my template fields were interrupted and spanned across two pages because of the page header, in 10.5 I would to define the page header without a trap/fields and it would ignore the page header and all would be well. I tried this in V14 but it is not behaving the same way. Can someone tell me if it works differently or know how I can get around this? Thanks for the help!!!
Answers
-
Hello M Clark,
That should still work - a multi-line detail trap should break nicely over a page header if you have defined a page header trap. You don't need to define any fields in the Page Header, although it's often useful to grab a page number or report run date if there is one.
A new feature in v14 is the Exclusion Trap - if you can define the page header block with a trap and mark it as an Exclusion template, then Monarch will ignore those lines completely.
Which approach is best depends on your data - if you'd like us to take look, we should be able to diagnose it from a screenshot or small sample.
Best wishes,
Olly
0 -
Altair Forum User said:
Hello M Clark,
That should still work - a multi-line detail trap should break nicely over a page header if you have defined a page header trap. You don't need to define any fields in the Page Header, although it's often useful to grab a page number or report run date if there is one.
A new feature in v14 is the Exclusion Trap - if you can define the page header block with a trap and mark it as an Exclusion template, then Monarch will ignore those lines completely.
Which approach is best depends on your data - if you'd like us to take look, we should be able to diagnose it from a screenshot or small sample.
Best wishes,
Olly
Well I tried the exclusion template but it didn't make a difference unless I defined it incorrectly.
Here is a screenshot of the issue where normally there is no issue picking up the second line of the detail but once in a while the page header will get in the way.
And this is how I tried to change the definition of the page header template using the exclusion trap.
Do you see anything?
0 -
Altair Forum User said:
Well I tried the exclusion template but it didn't make a difference unless I defined it incorrectly.
Here is a screenshot of the issue where normally there is no issue picking up the second line of the detail but once in a while the page header will get in the way.
And this is how I tried to change the definition of the page header template using the exclusion trap.
Do you see anything?
It seems that there might be one extra blank line after the Page Header which is causing the issue. You could try extending the PH template to 8 lines not 7?
0 -
Altair Forum User said:
It seems that there might be one extra blank line after the Page Header which is causing the issue. You could try extending the PH template to 8 lines not 7?
I thought that worked. It made it better but further down, it had an issue. Hmmmmm.....interesting.
0 -
Altair Forum User said:
I thought that worked. It made it better but further down, it had an issue. Hmmmmm.....interesting.
Okay looks like changing the trap line in the detail from a non blank to something specific helped. Thank you Olly.
0 -
Altair Forum User said:
I thought that worked. It made it better but further down, it had an issue. Hmmmmm.....interesting.
It might be helpful to Exclude all the blank lines as well - unless you are using these in Advanced Options to stop trapping multi-line fields. If you have irregular page header lengths, you might need a two-model approach, firstly grabbing whole lines to prepare a regularised report as a test export from a summary, then parsing that in a second model.
0
Altair Employee
