so I am trying to customise the colours for the legends. Basically what I am trying to do is to group the legends by colour. For example image we have refineries which are in different locations in the world. So for example if refineries 1, 2 & 3 are in Asia they should be coloured in green, and if refineries 4 & 5 are in Europe, then they should be coloured in blue. An example of this is shown below (created by excel):
Currently in PowerBI, this is my stacked chart:
So as you can see, the colours are dependent on the refineries, rather than on the locations (which are stored in a related Locations table).
Any idea of how this can be tackled in PowerBI please?
Much appreciated!
It would be very useful for BI developers if you could customize and format a little bit in Power BI using the built-in tools and expressions, something similar to SSRS, where you can set a color property based on the report data. Hope features like that be implemented soon.
As far as I know you can use Data Colors Pane:
Very manual and I think it breaks when new legends are added.
I've built a report in Reporting Services and when we browse to the report in Internet Explorer we want to be able to export the report in PDF format. It works, but it was cutting off the columns to the right and displaying them on the next page (in PDF) because the page was too wide. I changed the orientation to landscape and it still cut off the columns on the right. Then I changed the page size to legal paper and it fits on one page, but we want the report on letter size paper. Is there a way to compress the report to fit on letter size landscape?
Here is how to get a report to fit on a letter page:
Click on the blank space outside of your report
Look at the properties and find interactive size. Set it to 11,8.5in. Set your Margins to 0.5in, 0.5in, 0.5in, 0.5in
Click on the body and select properties. Set the width to 10in and something less than 7.5 for the height.
I was having this issue too. I set my margins to zero, which allowed me to print on 1 pdf page instead of 2.
When you develop report from SpagoBI Studio
change setting of Master Page (next to Layout).
No need to change orientation but you need to
increase the width of report according to your number of columns and column with.
make sure it is greater than sum of all column's width (table width)
This will solve the issues
I have scanned images with alpha channel that I need to compress. The images are drawings. Unfortunately their creation process creates random variation in color that compress poorly in PNG or even cause negative compression.
If I run filters over the data, I wipe out the text.
If I could split out all the pixels that are approximately a specific color into a separate layer, I could run filters without affecting the text.
There are four distinct colors I would like to split out.
The source image is indexed so there are not a lot of variation that needs to be split out.
Is this possible in Photoshop? If so, how?
-=-=-=-
I have not seen the format for a human readable color table. That would make things a lot easier. I have created some within photoshop and it is a PITA.
I was thinking about doing this manually at first then possibly automating it.
I have tried the magic want toll but I cannot get it to distinguish colors well. For example, I have purples and black. To get the thing to select all the purples, it grabs the blacks as well.
You can Scan image with Photoshop File > Import > WIA Support select your printer/Scanner and then scan your picture its come in actual color which you want and then you can compress its not distort your color
The best thing I could come up with was MAGIC WAND and disable the continuous setting.
Cut and Paste Special to a new layer.
I would preferred to select Polygon lasso or Magnetic lasso tool to select specific area.
Otherwise you select the command Select | Color Range and Select color with eyedropper tool
Best way to select all of a certain colour is to go to Select>Color Range
then select white with the eyedropper tool, this way it selects everything with the white value more accurately than manually with he magic tool, it gets all the little things you may miss. then use that to cut/paste into a new layer with ctrl+shift+v to put paste it in place :)
First of all, I am extremely new to sql reporting services, so my guess as to what is causing this issue could very well be off.
Basically, the first page of my reports spit out just fine, but when the 2nd+ pages hit, the width of the table is greater than 8.5 (which is what the interactivewidth is set to) inches because it clips off the page, and then creates a whole other page that looks blank, but if you look closely you will see the edge of the table from the previous page on the left side like so:
I suspect is might have to do with a possible word wrapping issue on this particular tablecell:
Because on the 2nd+ pages, that same tablecell displays as:
Which seems to be where the extra width is coming from that is making the table to wide for the page width. Thanks for any help.
SSRS doesn't allow column width to change dynamically, so you don't have to worry about that. The settings you need to adjust are the Page Size and the Margins. If the default margin on each side is 1 inch, you are left with 6.5 inches width to really work with. Try reducing the margin first, that should fix it.
I have a two-page SSRS report. When I exported it to PDF it was taking 4 pages due to its width, where the 2nd and 4th pages were displaying one of my fields from the table. I tried to set the layout size in report properties as width=18in and height =8.5in.
It gave me the whole table in a single page of PDF, but I am still getting the 2nd and 4th pages blank.
Is the way I am doing it incorrect? How else can I get rid of those blank pages?
In BIDS or SSDT-BI, do the following:
Click on Report > Report Properties > Layout tab (Page Setup tab in SSDT-BI)
Make a note of the values for Page width, Left margin, Right margin
Close and go back to the design surface
In the Properties window, select Body
Click the + symbol to expand the Size node
Make a note of the value for Width
To render in PDF correctly Body Width + Left margin + Right margin must be less than or equal to Page width. When you see blank pages being rendered it is almost always because the body width plus margins is greater than the page width.
Remember: (Body Width + Left margin + Right margin) <= (Page width)
Another thing to try is to set the report property called ConsumeContainerWhitespace to True (the default is false). That's how it got resolved for me.
After hours of struggling with this problem, I stumbled upon a solution that worked for me:
In SSDT (2012), I had originally had my Page Setup/Page units set to Centimeters. When I changed this to Inches, strangely enough, I was able to export my report to PDF without having every other page be blank.
It is better to do this on the design surface (Visual Studio 2012 is shown but can be done in other versions) first before calculating any maths when editing an SSRS document.
Below the following numbers in red circles that map to these following steps:
In the design surface, sometimes the editor will create a page which is larger than the actual controls; hence the ghost area being printed.
Resize to the controls. Visually look at the width/height and see if you can't bring in the page on the design surface to size it to the space actually needed by the controls and no more.
Then try to create a PDF and see if that fixes it.
If #3 does not resolve the issue, then there are controls requiring too much of the actual page size and going over in either length/width. So one will need to make the size of the controls smaller to accommodate a smaller page size.
Also in some circumstances one can just change a property of the report page by setting ConsumeContainerWhitespace to true to automatically consume the spaces.
The problem for me was that SSRS purposely treats your white space as if you intend it be honored:
As well as white space, make sure there is no right margin.
If the pages are blank coming from SSRS, you need to tweak your report layout. This will be far more efficient than running the output through and post process to repair the side effects of a layout problem.
SSRS is very finicky when it comes to pushing the boundaries of the margins. It is easy to accidentally widen/lengthen the report just by adjusting text box or other control on the report. Check the width and height property of the report surface carefully and squeeze them as much as possible. Watch out for large headers and footers.
I have worked with SSRS for over 10 years and the answers above are the go to answers. BUT. If nothing works, and you are completely stuffed....remove items from the report until the problem goes away. Once you have identified which row or report item is causing the problem, put it inside a rectangle container. That's it. Has helped us many many times! Extra pages are mostly caused by report items flowing over the right margin. When all else fails, putting things inside a rectangle or an empty rectangle to the right of an item, can stop this from happening. Good luck out there!
In addition to the margins, the most common issue by far, I have also seen two additional possibilities:
Using + to concatenate text. You should use & instead.
Text overflowing the width of the specified textbox. So if your textbox only holds 30 characters and you try to cram 300 in there, you might end up with extra pages.
Have you tried to see if there is any white space on the right of your report? If so you can drag it back to the end of your report and then drag the report background back to the same spot.
On the properties tab of the report (myReport.rdlc), change the "Keep Together" attribute to False. I've been struggling with this issue for a while and this seems to have solved my issue.
I recently inherited a report that I needed to make a few changes. After following all the recommendations above, it did not help. The report historically had this extra page, and nobody could figure out why.
I right clicked on the tablix and selected properties. There was a checkbox checked that said add a page break after. After removing this, it prints on one page now.
I fixed this issue by doing the following. ( Using the latest version of Report Builder )
Step 1.) Go to View Tab
Step 2.) Check the Properties checkbox
Step 3.) Click inside the body of your report (it will update values in properties tab)
Step 4.) Take not of the width here
Step 5.) Right click in the gray area outside the report and click report properties
Step 6.) Add your left + right margin to your body width ( if that equals 10 then make your width 11)
Step 7.) Save
If your report includes a subreport, the width of the subreport could push the boundaries of the body if subreport and hierarchy are allowed to grow.
I had a similar problem arise with a subreport that could be placed in a cell (spanning 2 columns). It looked like the span could contain it in the designer and it rendered fine in a winform or a browser and, originally, it could generate printer output (or pdf file) without spilling over onto excess pages.
Then, after changing some other column widths (and without exceeding the body width plus margins), the winform and browser renderings looked still looked fine but when the output (printer or pdf) was generated, it grew past the margins and wrote the right side of each page as a 2nd (4th, etc.) page. I could eliminate my problem by increasing colspan where the subreport was placed.
Whether or not you're using subreports, if you have page spillover and your body design fits within the margins of the page, look for something allowed to grow that pushes the width of the body out.
Make sure the designer in visual studio is not going beyond your max width. Hover over the right page border and drag to the left to make sure the page does not go over your desired layout.
I just reduced all elements Width shorter than 8 inch and it is being corrected,
I did that with mouse,
your report Body should be shorter than 8 inch.
I've successfully used pdftk to remove pages I didn't want/need in pdfs. You can download the program here
You might try something like the following. Taken from here under examples
Remove 'page 13' from in1.pdf to create out1.pdf
pdftk in.pdf cat 1-12 14-end output out1.pdf
or:
pdftk A=in1.pdf cat A1-12 A14-end output out1.pdf