SQL Server 2012 SSRS Export to Excel repeats border when no border is specified - by Josh George

Status : 


Sign in
to vote
ID 778470 Comments
Status Active Workarounds
Type Bug Repros 13
Opened 2/4/2013 8:19:40 AM
Access Restriction Public


When you have a financial report format in an SSRS table in SQL Sever 2012 (any version), and you try to export only to Excel (all others look fine) you get extra borders outlined where there is not supposed to be any.  For example, if you only want to set the bottom border to solid for row 2 of a table and you have a total of 10 rows, rows 2-10 will have a bottom border when exported to Excel.
Sign in to post a comment.
Posted by BSYourway on 3/25/2016 at 11:53 AM
Looks like this is still an issue. Can we have an update on a fix/work around. Thank you!
Posted by SQLSailor on 10/21/2015 at 8:14 AM
This issue seems to still exist with the latest SP of SQL Server 2014. Does Microsoft have any intention to mitigate the issue? This is preventing my organization from migrating to SQL Server 2014. I raised a seperate case with Microsoft regarding the issue. After much investigation I was ultimately referred to this ticket. Based upon the open date, it seems this is not a priority to Microsoft which is concerning and may force us to go with a different report generating vendor.
Posted by Mark A Stephenson on 9/11/2014 at 11:05 AM
I have reproduced this bug using:
    * SQL Server 2012 Service Pack 2
    * SQL Server 2014 RTM
    * SQL Server 2014 Cumulative Update 3

I tested with the following rendering extensions:
    * HTML
    * PDF
    * Excel
    * Excel Open Xml

Of the four rendering extensions only Excel Open Xml did not handle changing the border styles using an expression correctly.

Based on my testing the problem appears to be that once a textbox (or rectangle) has been assigned a border style other than “None” using an expression it cannot be changed back to “None”. It can however be successfully changed to one of the other border styles (i.e. Dashed, Dotted, Double or Solid).

To date I have found no work-a-round to the problem.
Posted by prom987 on 2/20/2014 at 2:46 PM
Any fixes or workarounds for this? Seems to be a problem in the Excel 2003 renderer and still reproduces in SQL2012 11.0.3393