Need Help trapping dynamic header and linking it to the details.
I need some help capturing the dynamic headers which have dates and will change each time we run the report. This is duplicated on each page of the report. The details of the report are 2 lines and would like to transform into 1 line.
Answers
-
Hi Anthony,
This should be easy enough I think. Could you please attach the actual report text or pdf file, along with the model file (.dmod) that contains any work you have already attempted on this file?
0 -
Nicholas_21406 said:
Hi Anthony,
This should be easy enough I think. Could you please attach the actual report text or pdf file, along with the model file (.dmod) that contains any work you have already attempted on this file?
Here you go. Thanks for helping! Had to zip the dmod since i cant add that as attachment
0 -
Thanks Anthony,
The output of Monarch is designed to have the same columns on every line. Therefore you can't easily have the columns on the first page named with dates from the header on the first page and columns on the second page named from dates from the header on the second page. There is only one column name for each column on the output report.
With some effort, it may be that you could coerce the report into another format, but that would fall under a Professional Services engagement.
Assuming there are the same number of columns on each page of the report, here is my recommendation. Add a Header Template that captures columns named PED 1 (Period End Date 1) through PED 8 (or any names that would be significant to you). When designing the report, later, we will be placing the PED 1 value next to the currency value. From the screenshot, you will see that each row has the same date value, but that is because there is only one page within this report.
Now let's go to your Detail record. Instead of naming the columns by the dates, which will change on every page, we will name them PEV 1 - PEV 8 (for Period Ending Value or some other name that will be meaningful to you). Note also that I have changed the record to be two rows in height, by replacing the sample text with two rows of data, and specifying the second row to be the trap row. I am also going to assume you would like to capture the Shop Order and Item Number.
Also, your Dpt and Loc fields were returning NULL because you defined them as numeric, but captured, for example "Dpt:201" instead of just "201".
To bring it all together, we change the order of the columns, so that PED 1 is next to PEV 1, and so on, by dragging column headers in Table Design.
So your final table would look something like the following:
I hope this gives you enough information to complete your report. I'm afraid I cannot give you the model depicted here as I am a Support engineer and so not permitted to do that. However, if you would like further help, please open a Support ticket, referencing this community question and a Support engineer would be able to walk you through this task.
0 -
Nicholas_21406 said:
Thanks Anthony,
The output of Monarch is designed to have the same columns on every line. Therefore you can't easily have the columns on the first page named with dates from the header on the first page and columns on the second page named from dates from the header on the second page. There is only one column name for each column on the output report.
With some effort, it may be that you could coerce the report into another format, but that would fall under a Professional Services engagement.
Assuming there are the same number of columns on each page of the report, here is my recommendation. Add a Header Template that captures columns named PED 1 (Period End Date 1) through PED 8 (or any names that would be significant to you). When designing the report, later, we will be placing the PED 1 value next to the currency value. From the screenshot, you will see that each row has the same date value, but that is because there is only one page within this report.
Now let's go to your Detail record. Instead of naming the columns by the dates, which will change on every page, we will name them PEV 1 - PEV 8 (for Period Ending Value or some other name that will be meaningful to you). Note also that I have changed the record to be two rows in height, by replacing the sample text with two rows of data, and specifying the second row to be the trap row. I am also going to assume you would like to capture the Shop Order and Item Number.
Also, your Dpt and Loc fields were returning NULL because you defined them as numeric, but captured, for example "Dpt:201" instead of just "201".
To bring it all together, we change the order of the columns, so that PED 1 is next to PEV 1, and so on, by dragging column headers in Table Design.
So your final table would look something like the following:
I hope this gives you enough information to complete your report. I'm afraid I cannot give you the model depicted here as I am a Support engineer and so not permitted to do that. However, if you would like further help, please open a Support ticket, referencing this community question and a Support engineer would be able to walk you through this task.
Do you have a video or walk through on how to make the rows to column headers?
0 -
I do not have such a video. To be clear, that is not what I was suggesting you to do. To best address this issue, perhaps you should open a Support ticket, by emailing to dasupport@altair.com.
0