Crystal Reports displays #### in numeric fields after upgrade - visual-studio-2012

I upgraded a Visual Studio solution containing Crystal Report files. Since the upgrade, the reports are displaying cross hatches (also called number signs: #####) when fields are too narrow to display their values. It was not doing that before. Is there any easy solution?
I have 9 reports, and although I tested them all, and fixed the width of the fields that appeared to be too narrow, when I use different data sets, I always find new cases where the field is too narrow to display the value.
What I have found out is that most of the time, only a few pixels are missing. On the old reports, I can even see that some numbers are cut a bit on the edge, but it does not prevent to read the values. The new version of Crystal Reports replaces those values by #####.
I guess I have two solutions: Enlarge all the fields by a few pixels or reduce the font size. I am not sure though if there is a way to do this globally, or if I have to do this by hand for every field.
Is there an easy way to tell Crytsal Reports, in such field, I want to be able to display let's say 5 digits using Courrier New 10 points?
I using Visual Studio 2012, .Net 4.5 and SAP Crystal Reports, developer version for Microsoft Visual Studio SP5. The old reports were from the time when Crystal Reports was embedded in VS.

If you can't format the fields to accommodate the largest values from the database, then you don't have many good options without moving to a non-printable-format. These two things might be useful to you:
Enable the clipping of those fields so that they no longer show the '###'. You can do this by right-clicking the number fields having this issue, selecting "Format Field", then go to the "Number" tab, then click "Customize". There should be a check box that reads "Allow Field Clipping". In my mind, this is pretty dangerous as values can appear differently than their true numerical values.
Set the fields to grow when the values are larger than their field size on the canvas. This will extend the fields down the page (I don't believe there is a way to do this horizontally) when necessary. You can access this option by right-clicking the fields, selecting "Format Field", then go to the "Common" tab and select "Can Grow". Note that this doesn't work for numeric fields so you will have to convert it to a string first.
EDIT: Now that I think about it, there is a way to extend a field horizontally, but it's slightly more difficult to pull off and will require calculating and passing the desired width via a formula. You can access this formula by right-clicking those fields, selecting "Size and Position" and clicking the formula button next to "Width".

Whenever I come across #### problem while displaying data to field, I just simply increase width of that crystal reports field

Related

How to create nested tiles in Power View

I am currently able to use the tile feature in Power View to view data much more quickly. However I haven't figured out a way to have nested tiles to further drill down into the relevant data.
For example, I want a tile strip at the top of my view of all the different "Projects." Once I click on a tile, I want to see all the relevant data for that project and have part of that container have a strip of tiles to show "Risks, Issues, Action Items, etc." and other items in a list. See image in this link (it is a non-working dashboard, but showing you all to get a better idea of the hierarchy).
Does any one know how to do this? I know I can use slicers instead for one of the levels or view filters but I want to be able to use tiles for both.
If you use a slicer within your tile it will almost do what you want. However, you wouldn't get the nice icons for warning & error to be the source of selection. You could make it more visual by separately having a table that includes the images so that when a user selects a slicer value, it shows the appropriate icon.
HTH,
-Lukasz
In the September Power BI update they've added te possibility to: Drill Up/Down for column and scatter charts in Reports.
Check out: Changelog

Report Builder 3.0 / VS2012 - How does one create a fixed-sized detail area of a report?

I am having some issues with Report Builder 3.0 and VS2012 in creating a invoice-like report that contains a fixed-sized section where detail rows will display. This section must be of fixed size so that each rendered report page will fit in a specific space regardless of the number of items. Items that would not fit then print on a new report page with the header and footer repeated.
I am not able to accomplish making the detail area a fixed-size. After searching for help and only coming up with some old (and unanswered) MS TechNet questions, I took the advice of this TechNet article which suggests using a rectangle inside of a tablix cell, then placing a detail tablix inside of the rectangle to achieve this effect.
This practice does allow me to add any amount of whitespace to the report, but it does not remain a fixed-size. On rendering the report, the rectangle will increase in size for each detail row (even though the rectangle is already big enough to fit the row), resulting in anything below the rectangle to be pushed onto new and unwanted pages. The rectangle doesn't have a "CanGrow" property to prevent this.
I have tried setting the "CanGrow" property on the detail tablix cells to "false". This only limits the actual cell from applying text wrap and expanding to fit cell contents; it doesn't appear to affect the rectangle. I have also set the "CanGrow" property on the parent tablix cell to "false", but this has no effect. Incidentally, I found that when I add a rectangle inside of the parent tablix cell, the "CanGrow" property will reset to "true".
To rule out an issue with Report Builder, I attempted to create the same report in VS2012 (as a .rdlc). I encountered the same design problems.
I have four questions:
Is this the correct way to go about creating the effect I need?
If so, what part am I missing?
Is there a another solution?
Are SSRS reports capable of this at all?
Here's a visual example of what I'm trying to create:
To fix your issue you should change the ConsumeContainerWhitespace property of the report to True.
ConsumeContainerWhitespace Link
This will also fix white-space problems with reports created in SSRS 2005 as in this version whitespace was automatically consumed.
See SSRS 2008R2 changes

Crystal Reports: controlling cell padding using formula in cross tab

I am working on a crystal report in VS 2012. I have a cross-tab in it which is displaying required data. My problem is when I am getting less no. of rows, then its shifting upwards, leading a blank space in rest of the page.
Now, I want to set cell padding of cross-tab using some formula, so that I can increase some vertical spacing of summarized fields in order to make my report look better.
If anybody can tell me how to achieve this?
Here is a snap of my report:-
Report Card
Thanks,
Prakhar Mishra

How to specify the width of site column in a list?

I have developed a list in SharePoint. While entering new item in it, like name, if I keep on typing it gets spread over a line making the width of cloumn spread over page. I want to limit the width of site column so as the column's value spreads over multiple lines instead of spreading over one. How can I do this setting?
This is not a setting you can configure in SharePoint. You will need to write some custom code using css and possibly javascript that will set the width of the column. You can make a change like this in SharePoint Designer.
You must use min-width (CSS) in your block.
You have to create custom XSLT for this. There you have loop all the column and need to specify the overflow:auto, hidden,.. CSS property. So it automatically get effect based on your internal name of the field.
So whereever you have the field it automatically get affected. If it for one single view you can use JavaScript to achieve this but this is not right way to do.
The data you are entering can be displayed in many ways. Today in a table format, tomorrow in a dropdown etc. You should distinguish between:
limiting the amount of data that can be entered in a site column (can be done in SharePoint alone, when you design your list)
limiting the wrapping of the words in a table cell today or trimming the values in a dropdown tomorrow (can be done using HTML/CSS "nowrap" if you display the list values in a browser app, or differently if you show the values in a WinForms app)

How to force a textbox to split, rather than move to a second page in SSRS 2005 (PDF Export)?

This question is a follow up to my original question, I've done a bit more reseach, i narrowed a problem down quite a bit.
I've also uploaded a sample .rdl to illustrate the problem
I've got the following report setup: a header (image in the body), two textboxes, and a footer.
First textbox has a little bit of text, and second textbox has lots of text. Second textbox can fit on one page by itself, but won't fit on the page with my header and the first textbox.
The problem is that for some reason, the second textbox in the report is unaware of other contents of that same report, and as long as that one textbox fits on one page - it will be moved to the second page. (once the textbox grows larger than 1 page - it will split, and will achieve the desired behavior)
Desired behavior is to split the second textbox, and keep as much text on the first page as possible, and move the rest to the second page.
I'm not sure about v.2005 but in v.2008 you can set a textbox property: KeepTogether to false.
This will fit as much text on the first page than the rest on the second page.
This is pretty standard behaviour in SSRS. Like many issues with the Reporting engine, you have to trick it.
In this case you could try to provide the 'lines' for the second text box as individual rows in a Detail, then use a repeater or table to display them. Alternatively you could break on 'paragraph'. Unfortunately you'll have to do this in your data source, probably in a stored procedure, depending on how you're getting the data to the report.
If appropriate you could look at client-side reporting (.rdlc files), which allows you to pre-process the data in a .NET application, although setting up for printing can be more complex.

Resources