August 8, 2008 at 6:56 am
I have report model deployed on the server. I can launch the report builder and design a report. But when I click on the filter and drag a field to the filter area it does not populate the dropdown list. It just keeps a textbox there. so when I run the report instead of selecting a value from dropdown I have to manually write down the parameter value. In my model I have only two tables related to each other using primary key/foreign key. I dont understand why it is not creating a drop down list for filter parameter. In report model I have tried to set "InstanceSelection" property to "DropDown" and redeployed the report model. It did not fix the issue.
can anyone please help me understanding the logic of populating dropdown? I know RB automatically populates filter drop down, but something is wrong with my model or is there something I am doing wrong?
February 3, 2011 at 8:41 am
I am having a similar problem. Using SQL 2008 and RB 2.0. I set one entity's InstanceSelection to MandatoryFilter, but I am never getting the error message that I need to include a filter. At what point in creating a report am I supposed to get this error? Ideas why I am not getting this error? I have added fields from that entity to the report. I can run it in RB and also from Report Manager. Any help would be greatly appreciated!
Thanks
Melissa
February 3, 2011 at 9:07 am
This is something that you need to specify in BIDS while creating report model. You need to go to report model select attribute of the entity in the MODEL. Each attribute has individual properties. You need to highlight the attribute that you need filter on and on the property window there is a property called "ValueSelection" or something similar. Set that property to "List" or "DropDown".
February 3, 2011 at 10:00 am
Thanks deveshnj. My problem is actually just a little different than yours. I am trying to set the InstanceSelection property on the entity as a whole, not an attribute. I have set it to MandatoryFilter, but am not seeing any change in behavior.
February 3, 2011 at 10:07 am
Not an expert here but my guess is, InstanceSelection property will come into effect when you pull entire entity (not attrubites from the entity) on the report designer area (in report builder). So for eg you have "Employee" entity and it has "EmpID". "Name", "DOB" etc attributes. now when you pull only "EmpID" or "Name" or "DOB" on the report, it will not ask you to have filter. but on the other hand, if you pull "Employee" entity on the report, it might ask you to put filter . As I said earlier, I havent tested this out but just throwing a guess.
Thanks,
Devesh
February 3, 2011 at 10:36 am
You are a genius! I thought I was losing it there for awhile, thanks for bringing back my sanity. Although unfortunatly that makes this functionality not as useful. 🙁 Thanks again for your help!
February 3, 2011 at 10:48 am
Glad that I could help. 🙂
Sad that Report Builder functionality did not help. :crying: I had same problem back in 2008 when I was trying to find a way to make filters on attributes mandatory. The main reason behind all my effort was, The report was there sitting on the server but when the user runs it w/o filter, it used to timeout after couple of minutes. I could not figure out clever way to address the problem instead designed the same report in report designer with mandatory filters. (not good practice though. I am doing user's job) I can totally understand the grief.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply