Showing posts with label exports. Show all posts
Showing posts with label exports. Show all posts

Tuesday, March 27, 2012

Excel Exports Hidden Images

Hello,
I think this may be a bug with SSRS 2005 but wanted to verify in case anyone
has a remedy. My report contains a table with an image on the detail row
whose visibility is toggled based on a value. Everything works as expected
when viewing the report onscreen or exporting to PDF. However, the Excel
Export ignores the visibility expression and displays the image for every
detail row. Any thoughts or workarounds?
Thanks in advance!
KathyOn Jul 6, 10:44 am, Kathy <K...@.discussions.microsoft.com> wrote:
> Hello,
> I think this may be a bug with SSRS 2005 but wanted to verify in case anyone
> has a remedy. My report contains a table with an image on the detail row
> whose visibility is toggled based on a value. Everything works as expected
> when viewing the report onscreen or exporting to PDF. However, the Excel
> Export ignores the visibility expression and displays the image for every
> detail row. Any thoughts or workarounds?
> Thanks in advance!
> Kathy
As far as I know, you are correct. Hopefully this will be corrected in
a future SP or in SSRS 2008. Sorry that I could not be of further
assistance.
Regards,
Enrique Martinez
Sr. Software Consultant|||Thank you for the quick response. Have a lovely day!
"EMartinez" wrote:
> On Jul 6, 10:44 am, Kathy <K...@.discussions.microsoft.com> wrote:
> > Hello,
> >
> > I think this may be a bug with SSRS 2005 but wanted to verify in case anyone
> > has a remedy. My report contains a table with an image on the detail row
> > whose visibility is toggled based on a value. Everything works as expected
> > when viewing the report onscreen or exporting to PDF. However, the Excel
> > Export ignores the visibility expression and displays the image for every
> > detail row. Any thoughts or workarounds?
> >
> > Thanks in advance!
> > Kathy
>
> As far as I know, you are correct. Hopefully this will be corrected in
> a future SP or in SSRS 2008. Sorry that I could not be of further
> assistance.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||On Jul 9, 8:38 am, Kathy <K...@.discussions.microsoft.com> wrote:
> Thank you for the quick response. Have a lovely day!
> "EMartinez" wrote:
> > On Jul 6, 10:44 am, Kathy <K...@.discussions.microsoft.com> wrote:
> > > Hello,
> > > I think this may be a bug with SSRS 2005 but wanted to verify in case anyone
> > > has a remedy. My report contains a table with an image on the detail row
> > > whose visibility is toggled based on a value. Everything works as expected
> > > when viewing the report onscreen or exporting to PDF. However, the Excel
> > > Export ignores the visibility expression and displays the image for every
> > > detail row. Any thoughts or workarounds?
> > > Thanks in advance!
> > > Kathy
> > As far as I know, you are correct. Hopefully this will be corrected in
> > a future SP or in SSRS 2008. Sorry that I could not be of further
> > assistance.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
You're welcome. Let me know if I can be of further assistance.
Regards,
Enrique Martinez
Sr. Software Consultant

Monday, March 26, 2012

Excel Destination appends the excel file everytime a package is executed

i have an SSIS package that exports to an excel file. This works fine. the problem is that it appends the data instead of overwriting the file. Is there any way to overwrite the file like you can with a flat file? I have to email the file everyweek and don't want to have to clear it out manually. Any help would be appreciated

Perhaps you can use an Execute SQL statement with a delete statement before the data flow task. That way you delete existing rows before loading the new one.

Update: I just tried that and did not work:

[Execute SQL Task] Error: Executing the query "delete FROM [Sheet1$]" failed with the following error: "Deleting data in a linked table is not supported by this ISAM.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

So, another option may be to have an empty copy of the file that you copy/rename evry time the package run. You can use File system task in control flow for that.

|||

Pamela,

You could also use a Execute SQL task to create a new excel file on every execution of the package. I have posted an step by step guide on that:

http://rafael-salas.blogspot.com/2006/12/import-header-line-tables-_116683388696570741.html

I hope you find it helpful