Thursday, March 29, 2012
Exporting Report Data to Case Management System
that enable clients to drill down to case level which they love. The problem
is that now they all want to be able to "push a button" and send the cases to
a case management system. I know how to write the code to send the cases to
the case management system tables but I don't know how to enable the client
to be able to trigger it from the report interface. Any assistance would be
much appreciated!Well this depends on how you want to do it... right now I assume they view
the reports from a browser right? If so, you may want to look into
customizing a front end to view the reports - or you can simply create a
smart client where you have a button on a form and the reports are listed
that can be exported to the case management system.
The last option is to create a delivery extension, which I think would be
the best thing to do, you select the report, and the new output to render to
if you will. :)
=-Chris
"St Matthew" <StMatthew@.discussions.microsoft.com> wrote in message
news:1BCF18A3-5568-41F7-B69B-A948828A0625@.microsoft.com...
>I work for a large government organisation and I have built several reports
> that enable clients to drill down to case level which they love. The
> problem
> is that now they all want to be able to "push a button" and send the cases
> to
> a case management system. I know how to write the code to send the cases
> to
> the case management system tables but I don't know how to enable the
> client
> to be able to trigger it from the report interface. Any assistance would
> be
> much appreciated!
Exporting Report Builder Tabular Report to CSV
A simple tabular Report Builder report was written to feed another system that requires quoted CSV. I have two issues when exported:
1) I can't get control over the exported column names. Currently, they are exported as "FIELDNAME_Value".
When I try to change the column headings in the designer, it has no effect on the exported column names
When I create a New Field and specify my desired column name (e.g., COMPANY), the export appears as COMPANY_Value.
How do I control these names for the CSV export?
2) The spec calls for quoted text. In my export, only values with special characters are quoted.
Thanks in advance.
-DRB
1) The CSV renderer gets the column names from each TextBox's DataElementName property. This property is exposed though Report Designer in VS.NET, but not through Report Builder. If you want to control the CSV columns you'll need to open the report in Report Designer, set DataElementName, and then redeploy back to the server.
2) The CSV renderer only qualifies values when they values contain the field or record delimiter. There isn't a way to force quotes around every text value.
I hope this helps.
-Chris
|||Chris:
Thank you for the lead on the CSV column header name. It didn't quite work. Here's what I did:
1) From Report Builder, Save to File.
2) Move RDL to server.
3) On server, launch Visual Studio and open a new Report Services project.
4) Add the RDL to the project. Set the DataElementName property on every element.
5) Choose File > Save [filename] As to save updated RDL.
6) Move updated RDL back to local client and Load from File in Report Builder.
7) Run and export the report.
In my experience, the exported column heading did not change. Here's a snippet from the RDL and from the CSV:
<TableCell>
<ReportItems>
<Textbox Name="SITEADDRESS_Value">
<DataElementOutput>Output</DataElementOutput>
<ZIndex>5</ZIndex>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<FontSize>8pt</FontSize>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BackgroundColor>White</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
<Language>en-US</Language>
</Style>
<CanGrow>true</CanGrow>
<DataElementName>BUSINESS STREET</DataElementName>
<Value>=Fields!BUSINESSSTREET.Value</Value>
</Textbox>
</ReportItems>
From the CSV header row:
FACILITYNAME_Value,SITEADDRESS_Value,CityNameSiteAddressCITYNAME_Value,STATE_Value,ZIP_Value,FAX_Value,PHONE_Value
As you can see, the column heading still took its name from the Name property (best I can tell).
Please advise.
-D. B.
|||Report Builder would open report from server, not from disk. In Visual Studio, you are saving report to disk, not deploying it to the server. Try deploying it to the report server from VS.NET and checking if this your header comes out as you expected in CSV, and then opening it in Report Builder.
CSV renderer always takes the name for the column from <DataElementName>, if present.
|||Thank you Dennis:
I may have a new related related challenge. When I attempt to publish and run the report from within VS as directed, I receive the following error:
An error occurred during local report processing. The definition of the report /{report name} is invalid. The DataElementName property for the Textbox SITEADDRESS_Value contains "BUSINESS STREET", which is not a CLS-compliant identifier.
I appreciate that the space is the source of the error... but (back to my original post), my customer requires a CSV file with column headers such as "BUSINESS STREET".
Any other ideas?
-D.R.B.
|||Unfortunately, DataElementName has to be CLS-Complaint, so you can't have spaces in the column name. Best available alternative is "_" character ("BUSINESS_STREET").
Monday, March 19, 2012
export/import a non system stored procedures from one DB to another
Hello, I want to export/import a non system stored procedures from one DB to another. How Should I proceed ?
Thanks in advance.
have you considered using the Transfer SQL Server Objects Task? http://msdn2.microsoft.com/en-us/library/ms142159.aspxMaaloul wrote:
Hello, I want to export/import a non system stored procedures from one DB to another. How Should I proceed ?
Thanks in advance.
Friday, February 17, 2012
Export System Catalog info
Hello,
I'm looking for a solution that will the extraction of system catalog information into either Excel or visio. We are looking to do this for documentation purposes. Is there a way to do this on the fly or do I need to run a view and then copy and past the information.
use sql Scripting. If the instance is SQL 2005 , then SQLCMD and if it is 2000 then OSQL.
SQL 2005 - sqlcmd -q"Exec sp_who2" -o"sp_who2_as_on_date.text"
SQL Server 2000- OSQL -q"Exec sp_who2" -o"sp_who2_as_on_date.text"
Check this
Madhu
|||If not you can set the query editor on SSMS to post the results to file by stating to comma seperated values.