Visual Studio 2008 - unable to copy and paste textboxes in SSRS reports with Custom Code after 2008 R2 SP2 upgrade - by Scott Ryan Fitzpatrick

Status : 


Sign in
to vote
ID 767968 Comments
Status Active Workarounds
Type Bug Repros 16
Opened 10/18/2012 10:49:45 AM
Access Restriction Public


After upgrading from SQL Server 2008 R2 to R2 SP2 + Cumm Update 2 (10.50.4263), when using Visual Studio 2008 (9.0.30729.4462 QFE)  to create new reports, we cannot copy and paste multiple textboxes in a tablix, and receive a popup error stating "Report Builder was unable to paste successfully"   

This error only occurs howerv when a report contains ANY textbox expressions with custom code.  
 ex. "=Code.AddTwoNumbers(1,2)"   Once the Custom Code textbxes are deleted you can cut and paste at will.

Confirmed on:
     Windows 7, 64-bit 
     Windows Server 2003 SP2, 32-bit
     Windows Vista 32-bit (was using only SQL 2008 R2 SP2 Express advanced here though)

Sign in to post a comment.
Posted by Jan van Egmond on 5/19/2016 at 2:44 AM
same error still pops up in ssrs sql 2014, cause is still the same too
Posted by Rafal Ziolkowski - CapGemini on 1/8/2016 at 5:07 AM
Any signs of fix? I am working as consultant and very often working with reports with hundreds fields with expressions - it is definitely time consuming to work around this issue or creating everything from scratch when you have working parts.
Posted by ageneralist on 10/7/2015 at 9:56 AM
Seems like Microsoft doesn't dog food the Report Designer in Visual Studio. If they are, they have a lot patience. This bug is driving me crazy because I have to use Custom Code on a regular basis.
Posted by Dr. AnGe on 9/10/2015 at 12:07 AM
Microsoft are really good at insvestigating. They are investigating this bug for about 5 years already with no result. They also have some good guys who write polite answers in fluent english. Both things help little to us who have to work with reports every day.
Posted by Mark (L) on 6/4/2015 at 6:21 AM
This is still a problem with SQL 2014 & Visual Studio 2013. It is really unbelievable that this still exists AND that you've marked is "Closed, won't fix".
Posted by Microsoft on 10/13/2014 at 6:22 AM
Thank you for submitting this feedback. We are investigating the issue and will update you when we have more information. In the meantime, if the issue is a critical business interruption please contact Customer Support Services.

Michael Griscom
SSRS Tiger Dev
Posted by KajaMoinudeen on 10/9/2014 at 7:10 AM
For the benefit of those looking for a work around - I tried deleting the cells which uses the custom code , copied the matrix ,did a Ctrl+Z to get the deleted cells back and then pasted the matrix without the coded cells.

It isn't much but still saved me a lot of rework.
Posted by b5lurker1 on 7/28/2014 at 1:45 PM
Unacceptable that this bug is still around in SSDT 2012 and 2013. Just ran into with my SSRS 2012 report that I was able to copy and paste large sections of before adding a Code. reference. Workaround shown does work, but what a pain!
Posted by SourabhAgarwal on 3/25/2014 at 4:44 AM
This is a very annoying bug to have. Imagine if I have Copy/paste, 20-30 objects and every time I have to check the report for accuracy.
Posted by clausl on 12/13/2013 at 1:36 AM
This bug is both in VS 2012 and VS 2013
Posted by BI Baracus on 12/5/2013 at 6:05 PM
no big deal. my billion dollar client who is evaluating reporting services watched me as I had to do this for 25 fields. made their decision a little easier.
Posted by jorgeghr on 10/3/2013 at 2:19 PM
I just came across this In SQL Server 2012 Data Tools too!

Sheeez Microsoft
Posted by Microsoft on 9/13/2013 at 12:03 PM
Thank you for this feedback. It will be forwarded to the appropriate team to consider a an enhancement in a future release.

If this is affecting a production deployment, please contact customer support.
Posted by Rob.Ford on 5/27/2013 at 4:42 PM
This is beyond annoying, it makes creating reports incredibly tedious, yes, please fix soon!
Posted by Nik A on 5/19/2013 at 7:59 PM
Mirorsoft please fix - this is very annoying
This bug also exists in SQL Server 2012 with Visual Studio 2010
VS: Version 10.0.40219.1 SP1Rel with the following installed:
Microsoft SQL Server Data Tools 10.3.21208.0
Microsoft SQL Server Reporting Services Designers Version 11.0.3000.0