Click through Report Parameter

Hi there.

I am having a problem where I have a Summary Report for a Region that lists out data for each community in that region (sample below):

West Region Count Community 1 N/A Community 2 14 Community 3 41 Community 4 25 Community 5 38 Community 6 67 Community 7 40 Community 8 52

I have navigation setup such that when I click on a Community (like Community_1 above), the detailed community report is called. I am passing CommunityID as a parameter to the community report. The community report has a CommunityID (literally) parameter setup. This seems fine, but when I click on a community from the Region report (for example, Community_1 above), the community report does not automatically get rendered, it makes me select a community before it renders. I must have something setup incorrectly, but can't figure it out. Any ideas would be appreciated.

I want the community report to be rendered based on the selected community without having to select it again.

Thanks, Mike

Sounds like the detailed community report has a parameter that does not have a default value set. That would be why it is asking for an input when it starts up. There is a parameter button on the navagation tab of the textbox properties window to map the default parameter from the original report to the report you are jumping. If there is only one "CommunityID" parameter in the jump too report that should be it. Might also check for a duplicate parameter that could have been accidently added without a default.

|||

Thanks for the response.

I do not have a default parameter set on the community detail report, but how do I do that when the report is dual purpose - 1. A click through where you pass a community id AND 2. a standalone community report where you pick your community from a list. Is this possible? It seems like it should be and I have something setup wrong still.

I do not see a place to setup a default parameter on the navigation for the textbox. I assume this is what you mean:

I click on parameters button on the navigation tab (where I have the community report selected). I pick CommunityID from the dropdown and set it = to =Fields!CommunityID.Value.

I think that should do it.

Also, I checked and I do not have a duplicate parameter. Other ideas?

Thanks, Mike

|||

To set the default parameter of the "Jump to report" from the original report:

In the original report:

Right click on the textbox with the jump to feature.

Select properties from the drop down.

Click navagation tab.

In the hyperlink action section beside the jump to report field is a parameters button.

Click it to open a parameter mapping window.

On this window you select a value from the original report to default into the parameter of the "jump to" report.

When filled in there should be two fields with values; one the parameter name from the "jump to" report and the other a parameter value which is a field in the original report.

If the jump to report is receiving the value correctly it will not ask for the value to be input when it is called up. If you are using the report for dual purpose it does not need to have a built in default value. The default can be blank and its value populated as described above.

|||

Thanks again for the response.

I have the default parameter setup correctly as you described, so I think it is not being passed correctly. The value I am getting from the database os a char(5), so it might not be handling the padding correctly or something. I am going to try it with another field that is an int and make sure that works... then I will know if it is that stupid char(5) value. Grrrrrrr.

Thanks, Mike

|||This issue is killing me. I can get clickthrough reports to work fine with other parameters (ints instead of char(5)). I have tried trimming the value before sending it etc. I have tried passing a specific community code (with and without padding) and that does not work. Anyone have ideas?|||Is there a way that I can see the actual value being passed?|||

Put the value in question into a textbox in the original report.

The data type does need to be the same for the field in both reports; might be able to workaround using some kind of type conversion in the parameter or sql stmt.

|||

OK, some more info...

I am passing the community code and it does contain spaces for padding up to the 5 chars, but I do not think that is the issue. I just tried setting up the report parameter on the community report and forced the default to be one of my community codes (non-queried) and the report still does not automatically populate. I still have to select a community code.

What would cause the report not to generate?

|||More info. I can get it to work fine when I do not have it setup to get available values from a query. I should be able to do that shouldn't I?|||

I figured it out...

In my dataset on the Community detail report which gets the list of available values, I had to cast the community id to be a varchar as below:

CAST(CommunityID AS varchar(5))

Then it worked fine. What a pain.

Mike