have a report build on top of a BEx query. The report parameters, which are actually variables in the query are dynamic and populated by LOVs created in Business View Manager. The issue I face is that I cannot set the default values to the parameters when I try to publish the report via Publishing Manager.
I published it without assigning defaults from Publishing Wizard. Set the default values from CMC and the values showed up. However when I view the instance from Infoview, the default values are not populated. been stuck all day on this one
Try to Save the report to BW role first and then Publish into BO repository using BW Publisher.
Related
Is it possible to set the value of a command parameter to a date calculation i.e 2 months from the date run without putting it in a sub-report and passing the values from a main report?
You can do this either using a subreport or in the calling application. No other way. You can check this video to see how it works in an application:
http://www.r-tag.com/Pages/Preview_RTagAndBOE.aspx
Jump directly to 2:12 or select "Parameter templates" in the menu. This software has a free version, which supports the default values so if changing the application is an option for you go and get it from here:
http://www.r-tag.com/Pages/CommunityEdition.aspx
If you developed your own application you can implement similar interface.
In ireport when clicking on preview, and you have parameters, you'll get a parameter box where you put a certain value to get specific record(s).Now i am trying to put specific values in the parameter box, so that the user would choose between it.
The same goal as in this so question : Loading promt box with parameters in iReport
However i want to do it without using Jasper Server. Is it possible to achieve this only from within IReport Designer?
You can do this,right click on the input control and select to add the local input control and provide id and name for the input control
Under the input control details select single select list of values if you have the list of values with you or if you want to add the data of a column as drill down select single select select query and extract that field.
This will help you to drill down the data.
Thanks and Regards
Megha
I'm pretty sure you can not do this in iReport preview. Have no clue what #Megha is refereeing to....
You can provide default value for your parameter through the <defaultValueExpression> tag and decide if you wan't it to prompt or not to prompt with the isForPrompting attribute.
Why can't we have select list, well I guess iReport is a tool for developers, so the preview is only to test the report. For customers jasper soft have developed the jasper report server.
And remember you can always develop your own interface (in swing or on the web)
I want the report to pick default date time values based on a location parameter the user picks, but the problem is that the date time parameters don't update when the user picks a different location. I made sure to put the location parameter above the date time parameters but it is still not functioning as I expect, what am I doing wrong here?
Unfortunately this is "by design".
Microsoft Connect - SSRS - default not refreshed for cascading parameters.
Posted by Microsoft in 2007: "As described, this is not
a bug. We do not re-evaluate the default value for a subsequent
parameter unless the selected value is no longer in the valid values
list. We do not know whether the current value was specifically
requested by the user or it is there because of the default. You could
make a case to have control over this behavior through some sort of
property but it is currently working as designed."
I think this is a bug in SSRS. But Microsoft have closed the issue. Please log onto connect and vote this to be fixed if it is affecting you too
Microsoft Connect - Your feedback improving Microsoft products.
Workaround / hack is here: Boyan Penev - SSRS Cascading Parameters Refresh: Solved.
However the hack only works if the dependent parameter has a LIST of valid values, and other users report that it only works for the first dependent parameter.
If the dependent parameter is free-form entry or a date, the hack cannot be used at all.
Consider putting your datetime values in a dataset with logic based on the location parameter
SELECT CASE #Location WHEN 'Paris' THEN GETDATE()+10
WHEN 'Berlin' THEN GETDATE()+11
WHEN 'New York' THEN GETDATE()+8
ELSE GETDATE() END as DefaultDate
Then set the date parameter default value to this dataset.
Unfortunately, SSRS does not refresh cascading parameters once they have been set. Other than reloading the report, the only way that I am aware of is to create a custom UI using the ReportViewerDialog.
I have found that if you use a stored procedure to render the child parameter, by passing in the parent selection, the dataset will get refreshed
I've been having the same issue, and realized it was a simple mistake causing this issue. Posting here for OP and anyone else searching for this issue.
You need to ensure that all parameters, in SSRS, are set to the correct value field, not the display field. You can replicate the cascading parameter issue that many have identified by simply selecting a "Name" field in the parameter default values instead of the "Value" field requested. This will populate the drop down correctly but nothing will be selected, and the cascade will stop. It may then appear as though the cascading parameters are not refreshing because of the Closed be Design issue.
In SSRS In Report Data tab, right click parameter and select
Parameter Properties.
Select Default Values.
Ensure that Value Field is set to the correct value for your sproc, not the value that you present to report users.
I'm using Crystal reports designer Version 11.
I have a report which calls a subreport and I have set up linked parameters.
The subreport is using a stored procedure.
I can't see how I feed to the parameters passed to the sub report into the stored procedure that is returning the data.
This is really late to the party, but I'm researching the same problem (I think) and have found a solution. In the main report, right-clck on the sub report and "Change Subreport Links".
In the top section, choose your parameter in the main report and click the right arrow to add to the "Field(s) to link to". In the bottom, sub-report section of the window, change the left side "Subreport parameter field to use" drop-down. It defaults to creating a new parameter in the sub report and you don't want to do that. You want to use an existing paramter (that was automatically added by using the stored procedure). In the drop-down choose that parameter that was auto created by the stored procedure.
Doing this means that you can have a parameter in the main report that you can automatically pass to the subreport which means you don't have to enter the same value for two separate parameters.
I hope this helps. It works great for me.
I understand this question is old but have found no satisfactory answer elsewhere. The simple solution I found is to implement the stored procedure from within a crystal command just like any other command sql. I could not get the parameters to show up in the bottom left drop downs no matter what. Something similar to below where ZNG_PROACTIVE_STREET_SWEEPS is the name of the stored procedure and the two parameters are what the stored procedure takes in.
[dbo].[ZNG_PROACTIVE_STREET_SWEEPS] #StartDate ={?begindate}, #EndDate = {?enddate}
After considering and then some searching, I take back my original answer.
Once you have parameters defined for the SQL Command, they are visible/available as parameters from outside the report. When you set up the links from the calling report to the subreport, the subreoprt parameters will be visible and available and you can link fields from the main report to those parameters.
A recent post in someone's blog covers the same activity with subreports driven from SQL Commands
Using SQL Commands and Parameters
I hope this helps and I hope that my original answer did not negatively affect your progress on your report.
Original answer
You cannot pass parameters to a stored procedure from report objects. The stored procedure will respond to CR Designer when you first reference the SP when you define the report. CR creates links to stored procedure parameters from the data source interface only, not from the report.
You will see an entry in the Parameters objects, but it will be read-only -- you can place it in the display section, but you cannot set it from report formulas, passed values, etc. Using formulas to process data before calling the stored procedure will not work, nor will trying to pass data through subreport links from the main report.
Using other design tools, you can have code that controls the data source interface, and processes data that is passed in parameters, but in CR Designer, you are pretty much left with the bare minimum options. You can right-click on the parameter and do things like set default values, set prompting text, set a pattern / mask for the format, but that's about it.
I am having some issues with dynamically changing report item visibility based on a report parameter.
Visibility is set correctly during the initial report run but WILL NOT change visibility of report items after the initial report run, regardless of if the report parameter changes. The expression I have on the Hidden attribute is below.
=IIF(Parameters!sr_emt_filter.Value = "ALL" And Parameters!sr_emt_direct_filter.Value = "ALL", True, False)
These are true report parameters and not query parameters. I currently have the parameters set to NEVER refresh the data sets as my process for this report is to pull all data on the first run and then use report parameters to filter down the results on an ad-hoc basis without re-querying the database (no need to discuss if this is a good approach or not, it is a requirement for what I am doing).
Any thoughts?