exporting multiple rows

I'm trying to set up a row that has 5 rows below it and when you click on the + it'll expand to show the five lines.

They're all set up to toggle based on the one row. It works online, but when I try to export it to anything, it only picks up the first detail row and leaves off the rest. I'm doing this for a bunch of reports, and they're all being emailed using subscriptions.

I've moved the detail rows around but each time it's just the first detail row that is exported.

Any ideas?

thx,

M@.

mattcushing@.gmail.com(noSpam)

Hello,

What formats are you trying to export to? Toggleable visibility is only supported in a few rendering extensions (HTML, Winforms, and in some cases Excel).

When you export to PDF or Image, those renderers honor the toggle state at the time the file is exported. So, if you have all of your toggleable items collapsed and then export to PDF you will only see the collapsed representation.

-Chris

sql

Export to Fixed Length Format text file without header row.

I am trying to generate a fixed-length format text file from a parameterised
SSRS report for my client and the only way that comnes close seems to be
to save as CSV with a single column query.
I have created a large, parameterised, UNIONed SQL statement to generate
the lines with the correct padding and alignment. This also concatenates
the columns so that the query effectively only returns a single column which
I can then Save As... CSV format. The problem with this is that I always
get a header row. (I concatenated in the query columns to avoid the commas
and quotes that come with CSV exports.)
I have experimented with the Noheader switch on the URL but the effectiveness
of this seems to disappear once the report a) stops for parameter input and
then b) renders to HTML before allowing me to save to CSV. I believe the
NoHeader option will only be effective if I determine my parameters ahead
of time and incorporate them into the URL also and render to CSV on that
URL as well.
All this combines to make for a complicated URL, certainly not something
my client would expect to create manually. Now I could write a small application
to generate offer them available parameters and then to this URL but I am
unsure if this effort is the way to go.
Options appear to be:
* bcp
* DTS
* application to allow users to input params and then generates the URL
* application to simply write the file and remove SSRS from the equation
* custom rendering extension
* purchase some kind of solution
It seems a lot of effort when I could just get them to manually deleted the
header row, however this approach is too unprofessional for my liking.
Ideally I would like to not have my client reliant on my code for new formats
or for when this format changes, hence a report writer based solution would
be great.
What is the best way to export to a fixed-length format text file from a
parameterised SSRS report?
cheers,
Paul.Unfortunately, as far as I am aware, there is no built in feature that
allows you to supress headers when exporting as csv.
As far as reporting services is concerned, the options are like you
said:
a) to build a custom renderer
b) to build a custom interface instead of using the report manager web
application
Both of these will require considerable effort to ultimately remove a
header row from a csv file
c) you could include a text box on the report with a hyperlink to
navigave to the required url (go to properties -> advanced ->
navigate). The user would then have to click on this text box to
download the report as csv with the appropriate noheaders tag. The
navigation url could be built dynamically using the report and
parameter information available from the formula fields, along with
the export format and noheaders tag appended on the end.
I have never tested this solution but it looks feasable if you are
happy for your users to click on a hyperlink to download.
Regards,
Rowen|||One suggestion is that
1. just make one more copy of the same report name it differently
2. In the copy of the report remove the header and keep the detail alone.
3. In the original report give a hyperlink using "Action" and name it
"Export to CSV" (or whater you like)
4. in the textbox ->Action, refer the copy of the report which is without
header using URL.
So what happens is users can also see the report with header and the link
will create the csv without header.
Amarnath
"Paul Ritchie" wrote:
> I am trying to generate a fixed-length format text file from a parameterised
> SSRS report for my client and the only way that comnes close seems to be
> to save as CSV with a single column query.
> I have created a large, parameterised, UNIONed SQL statement to generate
> the lines with the correct padding and alignment. This also concatenates
> the columns so that the query effectively only returns a single column which
> I can then Save As... CSV format. The problem with this is that I always
> get a header row. (I concatenated in the query columns to avoid the commas
> and quotes that come with CSV exports.)
> I have experimented with the Noheader switch on the URL but the effectiveness
> of this seems to disappear once the report a) stops for parameter input and
> then b) renders to HTML before allowing me to save to CSV. I believe the
> NoHeader option will only be effective if I determine my parameters ahead
> of time and incorporate them into the URL also and render to CSV on that
> URL as well.
> All this combines to make for a complicated URL, certainly not something
> my client would expect to create manually. Now I could write a small application
> to generate offer them available parameters and then to this URL but I am
> unsure if this effort is the way to go.
> Options appear to be:
> * bcp
> * DTS
> * application to allow users to input params and then generates the URL
> * application to simply write the file and remove SSRS from the equation
> * custom rendering extension
> * purchase some kind of solution
> It seems a lot of effort when I could just get them to manually deleted the
> header row, however this approach is too unprofessional for my liking.
> Ideally I would like to not have my client reliant on my code for new formats
> or for when this format changes, hence a report writer based solution would
> be great.
> What is the best way to export to a fixed-length format text file from a
> parameterised SSRS report?
> cheers,
> Paul.
>
>
>
>

Export to Excel Range

I have an SSIS package that exports data to a named range in Excel, except that instead of putting the data in the named range, it adds the first row of data to the first row below the range. The spreadsheet is not protected. Why doesn't the data get put into the named range?

When I'm done testing the SSIS package, I want to protect the spreadsheet and enable edit for the named range so that data can be written using the SSIS package. Will enabling the named range be necessary?

Dan

Dan:

I have not used named ranges in particular to populate data, but in general, when you use Excel as the destination you do not have the option to "overwrite" the data as you do in a Flat File destination. The problem you are experiencing could be because your package is updating the same Excel file during each run.

Does it always insert a new row one row below the named range? What happens when you run the package 2 or 3 times; each time it should be inserting new records at the n+1th row.

The issue of populating Excel destination has been discussed in previous threads and Rafael Salas apparently as a solution for it. I am not sure if his solution addresses populating Named Ranges particularly.

Rafael has a blog at blogspot.com, and is also listed in the Top Answerer box. When you click on his name it provides details of his profile.

|||The first step in the SSIS package is to execute a file server component that copies and renames a spreadsheet template to the spreadsheet I'm trying to populate. I've deleted the data range and removed any read-only settings. What has worked is to create and use a header range which then populates data in the first row immediately following. Thanks for the response and reference to Rafael Salas.

Export to Excel Range

I have an SSIS package that exports data to a named range in Excel, except that instead of putting the data in the named range, it adds the first row of data to the first row below the range. The spreadsheet is not protected. Why doesn't the data get put into the named range?

When I'm done testing the SSIS package, I want to protect the spreadsheet and enable edit for the named range so that data can be written using the SSIS package. Will enabling the named range be necessary?

Dan

Dan:

I have not used named ranges in particular to populate data, but in general, when you use Excel as the destination you do not have the option to "overwrite" the data as you do in a Flat File destination. The problem you are experiencing could be because your package is updating the same Excel file during each run.

Does it always insert a new row one row below the named range? What happens when you run the package 2 or 3 times; each time it should be inserting new records at the n+1th row.

The issue of populating Excel destination has been discussed in previous threads and Rafael Salas apparently as a solution for it. I am not sure if his solution addresses populating Named Ranges particularly.

Rafael has a blog at blogspot.com, and is also listed in the Top Answerer box. When you click on his name it provides details of his profile.

|||The first step in the SSIS package is to execute a file server component that copies and renames a spreadsheet template to the spreadsheet I'm trying to populate. I've deleted the data range and removed any read-only settings. What has worked is to create and use a header range which then populates data in the first row immediately following. Thanks for the response and reference to Rafael Salas.

Export to Excel missing last row

We have several reports in Excel that display fine in HTML, but when they
are exported to Excel the last Row is missing. There is a post dated 9/7 that
mentions the same problem, but was never answered...does anyone have any idea
what might be causing this or if there is a workaround?
ThanksI am having the same issue. I see there have been other posts about the
topic, but no answers. Anyone know any way to fix this? Thanks.
"kbradfor" wrote:
> We have several reports in Excel that display fine in HTML, but when they
> are exported to Excel the last Row is missing. There is a post dated 9/7 that
> mentions the same problem, but was never answered...does anyone have any idea
> what might be causing this or if there is a workaround?
> Thanks|||I made post on 10/14 and 10/20 with no replies. I'm hoping that Microsoft
will respond soon. This problem is causing my client to question the
reporting engine.
"kbradfor" wrote:
> We have several reports in Excel that display fine in HTML, but when they
> are exported to Excel the last Row is missing. There is a post dated 9/7 that
> mentions the same problem, but was never answered...does anyone have any idea
> what might be causing this or if there is a workaround?
> Thanks|||Has anyone tried to add a blank footer row to the table? This way if the bug
does occur it will just drop a blank footer and not your data. (I know this
is idea is just a band-aid not a fix but MS seems to be ignoring this
problem.)
I have not tested this theory myself because I have only seen this happen a
few times and each time I tried to dup the results everything worked fine.
Maybe someone out there has a report that has a regular problem that could
test it for me?
Tim
"Derek Howard" wrote:
> I made post on 10/14 and 10/20 with no replies. I'm hoping that Microsoft
> will respond soon. This problem is causing my client to question the
> reporting engine.
> "kbradfor" wrote:
> >
> > We have several reports in Excel that display fine in HTML, but when they
> > are exported to Excel the last Row is missing. There is a post dated 9/7 that
> > mentions the same problem, but was never answered...does anyone have any idea
> > what might be causing this or if there is a workaround?
> >
> > Thanks

Export To Excel Funny Result post Sp1

Hi
I have a report with which looked fine on the web page, and rendered to pdf.
But when export to excel, the cells are not alligned on the same row as the
report should be. It goes up and down 1 row randomly. The whole report just
look like zig zag mesh. Any one experience this issue?
Another issue is objects such as lists and text box where visibility are
toggled with an expression exports randomly. Some visible item are not
exported.
My report is a buch of list and text boxes align into rows. but as i said
before, after export to excel, each cell in the row randomly goes up and down
one row like a zig zag.
Any tips are appreciated.Sounds like the item spacing is interpreted as overlapping by the
export engine.
I'm having tons of fun with this same behavior right now. Spent 6
hours on it yesterday and today with unsatisfactory results. Boss
says "the users will have to live with it." Export results to PDF and
Excel are not consistent with each other, nor with HTML view, nor with
devenv preview. You have to strive for a balanced compromise, and one
at least of the views will look funky if you try to butt each item up
against another.
Don't depend on the design surface for item location and size. Even a
grid size of .025in won't help. Use the numbers in the properties box
for best results. For HTML rendering at least, the smallest size
increment that has meaning (according to BOL) is 0.2mm = 0.0078740 in,
round to 0.008in for use.
See "Design Considerations for Rendering" in the Books Online,
especially "Designing for Microsoft Excel Output."
EtU
happy for correction by the more knowledgeable
>Hi
>I have a report with which looked fine on the web page, and rendered to pdf.
>But when export to excel, the cells are not alligned on the same row as the
>report should be. It goes up and down 1 row randomly. The whole report just
>look like zig zag mesh. Any one experience this issue?
>Another issue is objects such as lists and text box where visibility are
>toggled with an expression exports randomly. Some visible item are not
>exported.
>My report is a buch of list and text boxes align into rows. but as i said
>before, after export to excel, each cell in the row randomly goes up and down
>one row like a zig zag.
>Any tips are appreciated.

export through DTS

Hi Everyone I got another problem every time I try to import data to Sql from Access 2000 it keeps give me an error message that says row 2271. Errors encountered so far in this tabel 1 insert error, column 8 (DOB, DBTYPE_DBTIMESTAMP), status 6: Data overflow. Invalid Character value for cast sepcification.

anyone got any suggestionsWhat is the record in row 2271?|||the same data in 2271 exsist in the rest of the database. columns Category, rehire, firstname..lastname..etc hiredate (date formats date/time)|||I guess, Derrick was asking what is the value of column 8 (DOB) at record 2271. It has to be different vs. let's say record #2270. Is the data type in access also datetime or it's a varchar?|||oh sorry the data in access is date/time data type, not varchar|||Here's where I'm going with this. Give us the CREATE TABLE statement for the SQL Server table you're importing into. Then give use the entire row of data from records 2270 and 2271. We should be able to see what's going on from that easily.