Scale of the graph changes when I export to PDF, mystery ...SOLVED

[lorenmario]

Hi!!!

I have a problem, I have a report with page break per store, this report displays four graphs that appear correctly when run in HTML.

When I export to PDF,  the page break is done, but it changes the scale of the graph, on every page graphics appear with the same scale, not respecting the filter store... Very strange ...

I need the scale is in accordance with the values ​​that appear on the Store page break.

Someone could tell me what might be happening?
Thank you!

[lorenmario]

Example of the report attached ...html version.

[lorenmario]

And when I export to pdf, the scale is changed to the higher value per store.

[velniaszs]

Well it is just a gues but if you are using bursting in your report it might be worth changing "axis range" - untick "Same range for all isntanve of chart" ( check attached picture)

[lorenmario]

Hi friend, thank you for responding.

I click the primary axis of the graph, and the property -> Axis range -> Automatic was selected, I tried to switch to manual, ran the report in PDF and did not work.

I do not use burst this report, only the page break.

The strange thing is that when I run the report in html appear correctly with the scale values ​​of the store, the way I need. But when I export to pdf Cognos change the scale for the largest store of value, and fixed all graphs with this scale.

You talked about the option "Same range for all of isntanve chart", but I have not found ...

Any more ideas?? You put a page break in the report that you did? You could try to help me?

Please help me! I need to deliver this report in pdf until tomorrow!
Thank you!
hug

[navissar]

Hi there,
could you post your xml here? I'd like to see how you set up the page break. If I'm right and you set it up using some sort of master-detail relationship, I may have an idea.

[navissar]

You know what, in the meantime, try this on for size:
1. Create a query ("Store") that contains only store.
2. Create a page set, set it up to have "Store" as its query.
3. Create a detail page, put your chart in there. Make sure the chart query has the store data item in it, and that it is either a part of the chart, or it is in the properties
4. Highlight the chart, edit it's Master Detail Relationship, link store data item in both ends.
5. highlight the y axis, click Axis range. The "Same range for all instances of chart" checkbox will be available, uncheck it.
6. Bob's your uncle.
I'm attaching a 10.1 xml based on samples.

[lorenmario]

Hi friend ... I rather the report is accessing a DMR model.

I made the page break, per store.
I added store info on the chart, and then did a filter, using the parameter of the page break, with the field that I inserted in the graph.
Look at the filter:
[CLUB] =? P1_generated-query?

(The parameter is generated by the page break)

Follows the XML attached ..
Thank you!

[lorenmario]

Forgot to say, as the report is dimensional, I'm using PAGE LAYERS ...

I took a print in the report design for you to see.

Tks! ;D

[navissar]

Yeah, I was afraid of that. Page layers are to page sets what context filters are to slicers - a stripped down, simplified version.
Try creating the report with a page set like I offered, this should solve your problem.

[lorenmario]

I will try to create the way you suggested, just a question ...

The report should be broken by Store and Type of Person, you asked me to create a query to Store, and I'll need to create another query for the type of person too? Or I can put the Person in same query Store?

Thank you! ;D

[navissar]

You can cut by both using page sets, and they can be in the same query.

[lorenmario]

Ok, I'm testing here as you inform your work out ...

[lorenmario]

I set the page break and master- detail as you asked me , I ran the PDF report , the scale of the graphs worked! ! Now I can see the change in scale for the store and also by type , all right !

The only question that remains is that the Crosstab was not considering the page break , so I set that " Grouping and Sorting " property page set with the store and person , the crosstab was filtered too! Finally !

The only problem is that when I run the report , every two pages with data appears one without ... I have two pages with data Store, and then appear on a page with no data, see the attached image. The report should be 54 pages ( 27 stores , 2 types of people = 54 pages ), but the pdf is generating 84 pages, because of these blank pages ...

Another doubt , as I no longer have the parameters generated in the page layer , I need to find a way to put in the report header the name of the Store and the Type of Person, you can tell me how to do it ?

Thank you for your precious help !  :)
hug

[navissar]

Hey,
I'm glad this works for you.
Let's start with the second question because it's easy: You want to drag in the objects from the pages sets query as singletons to where you had your title. Since it's all Master Detailed, you'll only see the relevant value. The sample attached has this.
Regarding the first issue, this shouldn't happen if you have data for all possible store/type of person combination, and there are no blank values. What I would do if I were you, I'd add the text showing exactly what you're looking at, and then run the report and see which values generate the empty pages, and filter them out of the master query.

Attached a sample for adding the values (Also shows how to nest the page sets)

[lorenmario]

Hi friend,

You helped me a lot, do not know how to thank you! I'm relieved ...
I used the singleton and solved the problem of the header titles, great!
I run the report and could see that besides the two types of person I need to show, had an empty third was what was wrong. I put a filter on the query page set and it worked!

Thank you very much! :-*
hug
Loren

[navissar]

Glad I could help. Have a good one.