- Right click on your data value field and select properties ( or on the chart properties box go to the Data tab , select a value and click Edit )
- Select the Point Labels Tab and click Show Point Labels.
- Choose the data label and the formatting style.
You can even customise the font attributes and point label positioning. However I stumbled accross a problem recently where if the values of the bars were significantly different from each other , some bars would not display the point labels.
The first thing I tried was to remove the Auto option and position the point label myself manually. This didn’t really help. I then tried adding Side Margins to the chart in order to make it display properly. This is useful if you sometimes have only a few range values and the chart does not quite look right. For example , if you have a chart of sales per month and you only have a months worth of data in the database, you get one large ugly bar the width of the chart. Adding side margins will always add some space on either side and make it look much nicer. The upshot is that adding the side margins to my chart cured the problem of the point labels not rendering on certain bars !! Go figure that one out. To add them in do the following :
- Go to the chart properties window
- Select your Axis and select Side Margins
Now the thing to remember here is that if you want margins on the left and right you have to enable it on the Y-Axis, and for the Top and Bottom do it on the X-Axis. ( I would have thought it would be the other way around ). So the default charts in Reporting Services do have a lot of functionality – you just need to play with all the properties to see what’s really possible. Of course , we’re getting Dundas charts in RS 2008 , and that’s something to really look forward to…..:)
The above illustrates a report where the actual table is less than 16 cms but the report width is not. You will still get extra blank pages when you print this or export to PDF. Make sure therefore that there is no extra space after the table on the right ( if not needed ).
The other way to control the report width is on the Report Properties Tab.
This is a useful window, lots of properties to set here
The above image shows the same report exported to PDF after the change is made. Easy as pie…….
You can also :
- Use Parameters or static fields instead of fields from the dataset ( This applies to most functions )
- Change the "d" ( which means compare days ) to "M" or "yyyy"
If it doesn’t work , remember that the values you are comparing must be date values. Use "CDate" to convert strings to Date values.
And remember , when you want compare a date to todays date , getdate() won’t work, since this is VB Script not SQL !! Use the Now() command as follows :
If the first date is smaller than the second date , the difference will be a positive number. You need to remember this since normally your expression for conditional formatting is normally something like :
|FormatDateTime(Parameters!Date.Value,1)||Tuesday, April 10, 2007|
…but the better way to do it would be to use …
2) The Format command and specify the exact format you require. For example…
So 3 M’s give you "Apr" ….anyway this is quite useful if you’re looking for Day/Month/Year , since the system will default to MM/DD/YYYY.
Using this you should be able to display the date format you want , or send through a particular format to a Stored Proc.
EDITED 22/08/2007 : If the Format Command doesn’t work , try converting the value to a date , eg.
3) A dialog box will pop up as shown below. Set the path to create the model , typically in your "Models" folder, and give it a name.
That should do it. Now when you open up Report Builder , you’ll see the model available on the right hand pane.
Now here’s a few things to remember.
1) Since you generated the model automatically , you cannot edit the entity names etc. afterwards to provide friendly names. Thus you will have to design the cube with user friendly names for the model to be generated accordingly.
2) Your parent-child hierachies are not exposed. Your Dimensions are created as Entities , with Members created as Fields. The good thing is that you still can get a drill down report with the correct heirachy if you create a matrix report and drag the Members in the correct order on either the row group or column group. This is shown below.
3) Calculated Measures and KPI’s that do not have an associated Measure Group will not appear in the Model.
For the full list , go to the following URL :
Well , I hope you guys find this useful. Just remember that Report Builder is NOT designed to be a slicing and dicing tool. But it still is great to give your users some functionality in terms of reporting off your OLAP sources.