versago3:dataview_setup

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
versago3:dataview_setup [2022/09/07 12:47]
dlee
versago3:dataview_setup [2023/07/14 12:38] (current)
dlee [Stored Procedure]
Line 63: Line 63:
  
 Store procedure parameters must be configured in the **//[[versago3:dataview_filters|Filters]]//** page. Store procedure parameters must be configured in the **//[[versago3:dataview_filters|Filters]]//** page.
 +
 +
 +<WRAP center round important 100% >
 +**Stored Procedure Limitations**
 +</WRAP>
 +Versago uses the view sys.dm_exec_describe_first_result_set_for_object to determine the store procedure's result set schema.
 +However, there are limitations with the system view that restricts the use of some store procedures in Versago.
 +The limitations include the use of temp tables and dynamic sql in the store procedure.
 +
 +Use the following query to determine if your store procedure will be suitable to be used as a Versago data source:
 +
 +<code>
 +SELECT name, system_type_name 
 +FROM sys.dm_exec_describe_first_result_set_for_object(OBJECT_ID(@StoredProcedureName), 0)
 +</code>
 +
 +
 ====View==== ====View====
  
Line 70: Line 87:
  
 A Data View can be configured to display a Crystal Report. When this option is selected, the Crystal Report definition file is uploaded to the Versago site and used as the presentation method. A Data View can be configured to display a Crystal Report. When this option is selected, the Crystal Report definition file is uploaded to the Versago site and used as the presentation method.
 +
 +<WRAP center round important 80% >
 +The data source used in the Crystal Report definition **must** be the same as that of the Versago Data View connection.
 +</WRAP> 
  
   * Select Crystal Report as the data source type.   * Select Crystal Report as the data source type.
Line 75: Line 96:
  
 The Crystal Report source file is copied from the original location to the folder “C:\Program Files (x86)\TWBS\Versago\Websites\Versago Administration Web Site\Reports.” A number is prefixed to the file name to ensure it uniqueness. If the Crystal Report needs to be modified, you can either modify this file or modify it elsewhere and re-register the new version in Versago. The Crystal Report source file is copied from the original location to the folder “C:\Program Files (x86)\TWBS\Versago\Websites\Versago Administration Web Site\Reports.” A number is prefixed to the file name to ensure it uniqueness. If the Crystal Report needs to be modified, you can either modify this file or modify it elsewhere and re-register the new version in Versago.
 +
 +---
 +=====**Need to review**=====
  
 ===SQL Server=== ===SQL Server===
 When designing a Crystal Report that will use a __SQL Server__ database as its data source, the report connection type must be **OLE DB (ADO)**. This connection type has three options for the data provider: **SQL Native Client**, **Microsoft OLE DB Driver for SQL Server**, and **Microsoft OLE DB Provider for SQL Server**.  Any of these options should work with Versago. When designing a Crystal Report that will use a __SQL Server__ database as its data source, the report connection type must be **OLE DB (ADO)**. This connection type has three options for the data provider: **SQL Native Client**, **Microsoft OLE DB Driver for SQL Server**, and **Microsoft OLE DB Provider for SQL Server**.  Any of these options should work with Versago.
- 
-The Crystal Report connection **must** be the same as that of the Versago Data View connection.  
  
 ===HANA=== ===HANA===
- 
 When designing a Crystal Report that will us a __HANA__ database as its data source, the report connection type be **ODBC (RDO)**.  **{{ :versago:b1h_90_ht_setupdsforcrl.pdf |This document }}** explains how to configure this type of connection for use with HANA.  Two options are described in the document.  Be sure to use the **B1CRHPROXY32** option.  Here is a sample connection string to use as a starting point. When designing a Crystal Report that will us a __HANA__ database as its data source, the report connection type be **ODBC (RDO)**.  **{{ :versago:b1h_90_ht_setupdsforcrl.pdf |This document }}** explains how to configure this type of connection for use with HANA.  Two options are described in the document.  Be sure to use the **B1CRHPROXY32** option.  Here is a sample connection string to use as a starting point.
  
Line 96: Line 117:
  
 ---- ----
 +**[[versago3:dataview#Add/Edit Data View]]**
  
 **[[versago3:Home|Home]]** **[[versago3:Home|Home]]**
      
versago3/dataview_setup.1662569230.txt.gz · Last modified: 2022/09/07 12:47 by dlee