It has to already be included in your parameter dataset.
Hope that what I'm trying to explain makes sense!įor 2005 - 2009 and your default value is returning a date in 2010, then it won't show up. This includes information like database connection information or a directory for the ERP attachments. It provides a comfortable user interface to configure the basic files required by Openbravo ERP to be built and to run properly. It has to already be included in your parameter dataset. The Setup Tool is used in Openbravo ERP for doing the initial configuration in custom and development installations. In other words, if your date query returns datesįor 2005 - 2009 and your default value is returning a date in 2010, then it won't show up. So even if you've set up your default parameter to use the fully-qualified member unique name and not just the visible value as Paul suggests, the value still has to exist in your parameter dataset. The default has to match the parameter value, not the parameter label. It's not very intuitive but the value you use for If you run your named set does it returnĪ value that looks EXACTLY like one of the values contained in ParameterValue field from your date query? If it returns a value that doesn't exist in ParameterValue then you won't get the default. When I run the report, the parameter dropdown is populated correctly with the appropriate values, but the default value is not selected.Īlso, the default value has to match one of the values in the Value field, not the Label field.
I then set the Default Value for the parameter to the following. I then have a named set in SSAS called which looks like the following: The Value field is set to ParameterValue and the Label field is set to ParameterCaptionIndented.
My report dataset is running the following query: I'm using SSRS 2008 running off a SSAS 2008 cube.