ssrs problem when adding fields to existing table

I have needed to add columns to tables SSRS is using as sources for reports.  I have found that if I add columns to the table but not at the end this breaks the report. It seems to key the position of the column in the tablel

So if I have the following original table:

Table1
Col1
Col2
Col3

And I want to change it to the following it works fine:

Table1
Col1
Col2
Col3
Col4

However the following breaks the report:

Table1
Col1
Col4
Col2
Col3

Is there a way I can add new columns within the table and refresh the dataset to find them?
canuckconsultingAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
ValentinoVConnect With a Mentor BI ConsultantCommented:
As kvwielink mentioned, adding fields to tables not should break reports as long as the queries for those reports are written using best practices.  Please post some more details on how exactly the report gets broken.  Do you get any error message for instance?  The queries would also help.
0
 
planoczConnect With a Mentor Commented:
They have to be added to the dataset first then check to see if they exists to show or hide that field.
0
 
Koen Van WielinkConnect With a Mentor Business Intelligence SpecialistCommented:
First of all, there is no reason why you would need to add a column in between other columns. Adding new columns to the end is perfectly fine, and there is no difference in performance. Sequence of columns is selected in your query, not because of the underlying table column sequence.
Secondly, adding a column to a table should not break the report. The dataset would still select the same existing columns. Unless you did something funky in your dataset query like an insert statement where you use select *. In that case because you changed the column sequence your insert statement would fail.
If you still can't work it out it would help if you can upload some sample data, your dataset query and the report RDL.
0
 
canuckconsultingAuthor Commented:
Hi guys,

The issue appears to be related to cached data stored in the associated .rdl.data files.  If I delete the file the report runs fine.

Cheers guys...I'm splitting the points and hope future searches will also note my comment.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.